Premises management configuration and control

ABSTRACT

Disclosed are methods, systems, and devices for management of a premises. The premises may comprise one or more devices, such as a gateway device, a control device, or a premises device. The gateway device may receive data and send the data to the control device. The data may comprise a command, an update, a configuration, or other information. Communication between the control device and any of the other devices at the premises may be configurable by a server device.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/750,976, filed Jan. 23, 2020, now U.S. Pat. No. 10,979,389 issuedApr. 13, 2021, which is a continuation of U.S. patent application Ser.No. 16/147,044, filed Sep. 28, 2018, now U.S. Pat. No. 11,159,484 issuedOct. 26, 2021, which is a continuation application of U.S. patentapplication Ser. No. 13/932,816, filed Jul. 1, 2013, now U.S. Pat. No.10,313,303 issued Jun. 4, 2019, which is a continuation in partapplication of U.S. patent application Ser. No. 13/925,181, filed Jun.24, 2013, now U.S. Pat. No. 10,339,791 issued Jul. 2, 2019,

and is a continuation in part application of U.S. patent applicationSer. No. 13/718,851, filed Dec. 18, 2012 now U.S. Pat. No. 10,156,831issued Dec. 18, 2018,

and is a continuation in part application of U.S. patent applicationSer. No. 13/531,757, filed Jun. 25, 2012, now abandoned,

and is a continuation in part application of U.S. patent applicationSer. No. 13/335,279, filed Dec. 22, 2011, now U.S. Pat. No. 11,113,950issued Sep. 7, 2021,

and is a continuation in part application of U.S. patent applicationSer. No. 13/311,365, filed Dec. 5, 2011, now U.S. Pat. No. 9,141,276issued Sep. 22, 2015,

and is a continuation in part application of U.S. patent applicationSer. No. 13/104,932, filed May 10, 2011, now abandoned,

and is a continuation in part application of U.S. patent applicationSer. No. 12/750,470, filed Mar. 30, 2010, now U.S. Pat. No. 9,191,228issued Nov. 17, 2015,

and is a continuation in part application of U.S. patent applicationSer. No. 12/637,671, filed Dec. 14, 2009, now U.S. Pat. No. 8,478,871issued Jul. 2, 2013,

and is a continuation in part application of U.S. patent applicationSer. No. 12/539,537, filed Aug. 11, 2009, now U.S. Pat. No. 10,156,959issued Dec. 18, 2018,

and is a continuation of U.S. patent application Ser. No. 12/189,788,filed Aug. 12, 2008, now U.S. Pat. No. 8,478,844 issued Jul. 2, 2013,

and is a continuation in part application of U.S. patent applicationSer. No. 12/019,568, filed Jan. 24, 2008, now U.S. Pat. No. 10,142,392issued Nov. 27, 2018,

and is a continuation in part application of U.S. patent applicationSer. No. 11/761,745, filed Jun. 12, 2007, now U.S. Pat. No. 8,635,350issued Jan. 21, 2014, each of which are hereby incorporated by referencein their entirety.

U.S. patent application Ser. No. 12/189,788 is a divisional of U.S.patent application Ser. No. 12/189,757, filed Aug. 11, 2008, now U.S.Pat. No. 8,473,619 issued Jun. 25, 2013,

and is a non-provisional of and claims the benefit of U.S. ProvisionalApplication No. 61/087,967, filed Aug. 11, 2008,

and is a non-provisional of and claims the benefit of U.S. ProvisionalApplication No. 61/023,496, filed Jan. 25, 2008,

and is a non-provisional of and claims the benefit of U.S. ProvisionalApplication No. 61/023,493, filed Jan. 25, 2008,

and is a non-provisional of and claims the benefit of U.S. ProvisionalApplication No. 61/023,489, filed Jan. 25, 2008,

and is a continuation in part application of U.S. patent applicationSer. No. 12/019,554, filed Jan. 24, 2008, now U.S. Pat. No. 7,911,341issued Mar. 22, 2011,

and is a non-provisional of and claims the benefit of U.S. ProvisionalApplication No. 61/019,162, filed Jan. 4, 2008,

and is a non-provisional of and claims the benefit of U.S. ProvisionalApplication No. 61/019,167, filed Jan. 4, 2008,

and is a non-provisional of and claims the benefit of U.S. ProvisionalApplication No. 60/987,359, filed Nov. 12, 2007,

and is a non-provisional of and claims the benefit of U.S. ProvisionalApplication No. 60/987,366, filed Nov. 12, 2007,

and is a non-provisional of and claims the benefit of U.S. ProvisionalApplication No. 60/968,005, filed Aug. 24, 2007,

and is a continuation in part application of U.S. patent applicationSer. No. 11/761,718, filed Jun. 12, 2007, now U.S. Pat. No. 7,711,796issued May 4, 2010,

and is a continuation in part application of U.S. patent applicationSer. No. 11/084,232, filed Mar. 16, 2005, now U.S. Pat. No. 8,335,842issued Dec. 18, 2012, each of which are hereby incorporated by referencein their entirety.

U.S. patent application Ser. No. 12/637,671 is a continuation of U.S.patent application Ser. No. 11/761,718 filed Jun. 12, 2007, now U.S.Pat. No. 7,711,796 issued May 4, 2010, which is a non-provisional of andclaims the benefit of U.S. Provisional Application No. 60/804,550, filedJun. 12, 2006, which is incorporated by reference in its entirety.

U.S. patent application Ser. No. 12/019,568 is a non-provisional of andclaims the benefit of U.S. Provisional Application No. 60/886,439, filedJan. 24, 2007, which is incorporated by reference in its entirety.

U.S. patent application Ser. No. 13/531,757 is a continuation in part ofU.S. patent Ser. No. 12/269,735, filed Nov. 12, 2008, now U.S. Pat. No.8,996,665 issued Mar. 31, 2015,

and is a continuation in part of U.S. patent Ser. No. 12/197,931, filedAug. 25, 2008, now U.S. Pat. No. 9,172,553 issued Oct. 27, 2015,

and is a continuation of U.S. patent Ser. No. 12/198,023, filed Aug. 25,2008, now U.S. Pat. No. 8,209,400 issued Jun. 26, 2012, each of whichare hereby incorporated by reference in their entirety.

U.S. patent application Ser. No. 13/311,365 is a continuationapplication of U.S. patent Ser. No. 12/197,895, filed Aug. 25, 2008, nowU.S. Pat. No. 8,073,931 issued Dec. 6, 2011, which is herebyincorporated by reference in its entirety.

U.S. patent application Ser. No. 13/335,279 is a continuation of U.S.patent application Ser. No. 12/269,767, filed Nov. 12, 2008, now U.S.Pat. No. 8,086,703 issued Dec. 27, 2011, which is hereby incorporated byreference in its entirety.

U.S. patent application Ser. No. 12/539,537 is a non-provisional of andclaims the benefit of U.S. Provisional Application No. 61/164,877, filedMar. 30, 2009,

and is a continuation in part of U.S. patent application Ser. No.12/269,585, filed Nov. 12, 2008, now U.S. Pat. No. 8,086,702 issued Dec.27, 2011, each of which are hereby incorporated by reference in theirentirety.

U.S. patent application Ser. No. 13/104,932 is a non-provisional of andclaims the benefit of U.S. Provisional Application No. 61/333,130, filedMay 10, 2010, which is hereby incorporated by reference in its entirety.

U.S. patent application Ser. No. 12/189,757 is a non-provisional of andclaims the benefit of U.S. Provisional Application No. 60/957,997, filedAug. 24, 2007,

and is a non-provisional of and claims the benefit of U.S. ProvisionalApplication No. 60/955,172, filed Aug. 10, 2007, each of which arehereby incorporated by reference in their entirety.

U.S. patent application Ser. No. 12/019,554 is a non-provisional of andclaims the benefit of U.S. Provisional Application No. 60/886,435, filedJan. 24, 2007, which is hereby incorporated by reference in itsentirety.

U.S. patent application Ser. No. 11/084,232 is a non-provisional of andclaims the benefit of U.S. Provisional Application No. 60/652,475, filedFeb. 11, 2005,

and is a non-provisional of and claims the benefit of U.S. ProvisionalApplication No. 60/553,932, filed Mar. 16, 2004,

and is a non-provisional of and claims the benefit of U.S. ProvisionalApplication No. 60/553,934, filed Mar. 16, 2004, each of which arehereby incorporated by reference in their entirety.

This application is a continuation in part of U.S. patent applicationSer. No. 15/588,206, filed May 5, 2017, which is a continuation of U.S.patent application Ser. No. 12/189,780, filed Aug. 11, 2008, nowabandoned, which claims the benefit of and is a non-provisional of U.S.Provisional Application 61/087,967, filed Aug. 11, 2008,

and is a non-provisional of and claims the benefit of U.S. ProvisionalApplication No. 61/023,496, filed Jan. 25, 2008,

and is a non-provisional of and claims the benefit of U.S. ProvisionalApplication No. 61/023,493, filed Jan. 25, 2008,

and is a non-provisional of and claims the benefit of U.S. ProvisionalApplication No. 61/023,489, filed Jan. 25, 2008,

and is a continuation in part application of U.S. patent applicationSer. No. 12/019,568, filed Jan. 24, 2008, now U.S. Pat. No. 10,142,392issued Nov. 27, 2018,

and is a continuation in part application of U.S. patent applicationSer. No. 12/019,554, filed Jan. 24, 2008, now U.S. Pat. No. 7,911,341issued Mar. 22, 2011,

and is a non-provisional of and claims the benefit of U.S. ProvisionalApplication No. 61/019,162, filed Jan. 4, 2008,

and is a non-provisional of and claims the benefit of U.S. ProvisionalApplication No. 61/019,167, filed Jan. 4, 2008,

and is a non-provisional of and claims the benefit of U.S. ProvisionalApplication No. 60/987,359, filed Nov. 12, 2007,

and is a non-provisional of and claims the benefit of U.S. ProvisionalApplication No. 60/987,366, filed Nov. 12, 2007,

and is a non-provisional of and claims the benefit of U.S. ProvisionalApplication No. 60/968,005, filed Aug. 24, 2007,

and is a non-provisional of and claims the benefit of U.S. ProvisionalApplication No. 60/957,997, filed Aug. 24, 2007,

and is a non-provisional of and claims the benefit of U.S. ProvisionalApplication No. 60/955,172, filed Aug. 10, 2007,

and is a continuation in part application of U.S. patent applicationSer. No. 11/761,745, filed Jun. 12, 2007, now U.S. Pat. No. 8,635,350issued Jan. 21, 2014,

and is a continuation in part application of U.S. patent applicationSer. No. 11/761,718, filed Jun. 12, 2007, now U.S. Pat. No. 7,711,796issued May 4, 2010,

and is a continuation in part application of U.S. patent applicationSer. No. 11/084,232, filed Mar. 16, 2005, now U.S. Pat. No. 8,335,842issued Dec. 18, 2012, each of which are hereby incorporated by referencein their entirety.

This application is a continuation of U.S. patent application Ser. No.16/147,044, filed Sep. 28, 2018, now U.S. Pat. No. 11,159,484 issuedOct. 26, 2021.

BACKGROUND

The field of home and small business security is dominated by technologysuppliers who build comprehensive ‘closed’ security systems, where theindividual components (sensors, security panels, keypads) operate solelywithin the confines of a single vendor solution. For example, a wirelessmotion sensor from vendor A cannot be used with a security panel fromvendor B. Each vendor typically has developed sophisticated proprietarywireless technologies to enable the installation and management ofwireless sensors, with little or no ability for the wireless devices tooperate separate from the vendor's homogeneous system. Furthermore,these traditional systems are extremely limited in their ability tointerface either to a local or wide area standards-based network (suchas an IP network); most installed systems support only a low-bandwidth,intermittent connection utilizing phone lines or cellular (RF) backupsystems. Wireless security technology from providers such as GESecurity, Honeywell, and DSC/Tyco are well known in the art, and areexamples of this proprietary approach to security systems for home andbusiness.

Furthermore, with the proliferation of the internet, ethernet and WiFilocal area networks (LANs) and advanced wide area networks (WANs) thatoffer high bandwidth, low latency connections (broadband), as well asmore advanced wireless WAN data networks (e.g. GPRS or CDMA 1×RTT) thereincreasingly exists the networking capability to extend thesetraditional security systems to offer enhanced functionality. Inaddition, the proliferation of broadband access has driven acorresponding increase in home and small business networkingtechnologies and devices. It is desirable to extend traditional securitysystems to encompass enhanced functionality such as the ability tocontrol and manage security systems from the world wide web, cellulartelephones, or advanced function internet-based devices. Other desiredfunctionality includes an open systems approach to interface homesecurity systems to home and small business networks.

Due to the proprietary approach described above, the traditional vendorsare the only ones capable of taking advantage of these new networkfunctions. To date, even though the vast majority of home and businesscustomers have broadband network access in their premises, most securitysystems do not offer the advanced capabilities associated with highspeed, low-latency LANs and WANs. This is primarily because theproprietary vendors have not been able to deliver such technologyefficiently or effectively. Solution providers attempting to addressthis need are becoming known in the art, including three categories ofvendors: traditional proprietary hardware providers such as Honeywelland GE Security; third party hard-wired module providers such asAlarm.com, NextAlarm, and uControl; and new proprietary systemsproviders such as InGrid.

A disadvantage of the prior art technologies of the traditionalproprietary hardware providers arises due to the continued proprietaryapproach of these vendors. As they develop technology in this area itonce again operates only with the hardware from that specific vendor,ignoring the need for a heterogeneous, cross-vendor solution. Yetanother disadvantage of the prior art technologies of the traditionalproprietary hardware providers arises due to the lack of experience andcapability of these companies in creating open internet and web basedsolutions, and consumer friendly interfaces.

A disadvantage of the prior art technologies of the third partyhard-wired module providers arises due to the installation andoperational complexities and functional limitations associated withhardwiring a new component into existing security systems. Moreover, adisadvantage of the prior art technologies of the new proprietarysystems providers arises due to the need to discard all priortechnologies, and implement an entirely new form of security system toaccess the new functionalities associated with broadband and wirelessdata networks. There remains, therefore, a need for systems, devices,and methods that easily interface to and control the existingproprietary security technologies utilizing a variety of wirelesstechnologies.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of the integrated security system, under anembodiment.

FIG. 2 is a block diagram of components of the integrated securitysystem, under an embodiment.

FIG. 3 is a block diagram of the gateway software or applications, underan embodiment.

FIG. 4 is a block diagram of the gateway components, under anembodiment.

FIG. 5 is a block diagram of IP device integration with a premisenetwork, under an embodiment.

FIG. 6 is a block diagram of IP device integration with a premisenetwork, under an alternative embodiment.

FIG. 7 is a block diagram of a touchscreen, under an embodiment.

FIG. 8 is a flow diagram for a method of forming a security networkincluding integrated security system components, under an embodiment.

FIG. 9 is a flow diagram for a method of forming a security networkincluding integrated security system components and network devices,under an embodiment.

FIG. 10 is a flow diagram for installation of an IP device into aprivate network environment, under an embodiment.

FIG. 11 is a block diagram showing communications among IP devices ofthe private network environment, under an embodiment.

FIG. 12 is a flow diagram of a method of integrating an external controland management application system with an existing security system,under an embodiment.

FIG. 13 is a block diagram of an integrated security system 1300wirelessly interfacing to proprietary security systems, under anembodiment.

FIG. 14 is a flow diagram for wirelessly ‘learning’ the gateway into anexisting security system and discovering extant sensors, under anembodiment.

DETAILED DESCRIPTION

An integrated security system is described that integrates broadband andmobile access and control with conventional security systems and premisedevices to provide a tri-mode security network (broadband, cellular/GSM,POTS access) that enables users to remotely stay connected to theirpremises. The integrated security system, while delivering remotepremise monitoring and control functionality to conventional monitoredpremise protection, complements existing premise protection equipment.The integrated security system integrates into the premise network andcouples wirelessly with the conventional security panel, enablingbroadband access to premise security systems. Automation devices(cameras, lamp modules, thermostats, etc.) can be added, enabling usersto remotely see live video and/or pictures and control home devices viatheir personal web portal or webpage, mobile phone, and/or other remoteclient device. Users can also receive notifications via email or textmessage when happenings occur, or do not occur, in their home.

Although the detailed description herein contains many specifics for thepurposes of illustration, anyone of ordinary skill in the art willappreciate that many variations and alterations to the following detailsare within the scope of the embodiments described herein. Thus, thefollowing illustrative embodiments are set forth without any loss ofgenerality to, and without imposing limitations upon, the claimedinvention.

In accordance with the embodiments described herein, a wireless system(e.g., radio frequency (RF)) is provided that enables a securityprovider or consumer to extend the capabilities of an existingRF-capable security system or a non-RF-capable security system that hasbeen upgraded to support RF capabilities. The system includes anRF-capable Gateway device (physically located within RF range of theRF-capable security system) and associated software operating on theGateway device. The system also includes a web server, applicationserver, and remote database providing a persistent store for informationrelated to the system.

The security systems of an embodiment, referred to herein as theiControl security system or integrated security system, extend the valueof traditional home security by adding broadband access and theadvantages of remote home monitoring and home control through theformation of a security network including components of the integratedsecurity system integrated with a conventional premise security systemand a premise local area network (LAN). With the integrated securitysystem, conventional home security sensors, cameras, touchscreenkeypads, lighting controls, and/or Internet Protocol (IP) devices in thehome (or business) become connected devices that are accessible anywherein the world from a web browser, mobile phone or through content-enabledtouchscreens. The integrated security system experience allows securityoperators to both extend the value proposition of their monitoredsecurity systems and reach new consumers that include broadband usersinterested in staying connected to their family, home and property whenthey are away from home.

The integrated security system of an embodiment includes securityservers (also referred to herein as iConnect servers or security networkservers) and an iHub gateway (also referred to herein as the gateway,the iHub, or the iHub client) that couples or integrates into a homenetwork (e.g., LAN) and communicates directly with the home securitypanel, in both wired and wireless installations. The security system ofan embodiment automatically discovers the security system components(e.g., sensors, etc.) belonging to the security system and connected toa control panel of the security system and provides consumers with fulltwo-way access via web and mobile portals. The gateway supports variouswireless protocols and can interconnect with a wide range of controlpanels offered by security system providers. Service providers and userscan then extend the system's capabilities with the additional IPcameras, lighting modules or security devices such as interactivetouchscreen keypads. The integrated security system adds an enhancedvalue to these security systems by enabling consumers to stay connectedthrough email and SMS alerts, photo push, event-based video capture andrule-based monitoring and notifications. This solution extends the reachof home security to households with broadband access.

The integrated security system builds upon the foundation afforded bytraditional security systems by layering broadband and mobile access, IPcameras, interactive touchscreens, and an open approach to homeautomation on top of traditional security system configurations. Theintegrated security system is easily installed and managed by thesecurity operator, and simplifies the traditional security installationprocess, as described below.

The integrated security system provides an open systems solution to thehome security market. As such, the foundation of the integrated securitysystem customer premises equipment (CPE) approach has been to abstractdevices, and allows applications to manipulate and manage multipledevices from any vendor. The integrated security system DeviceConnecttechnology that enables this capability supports protocols, devices, andpanels from GE Security and Honeywell, as well as consumer devices usingZ-Wave, IP cameras (e.g., Ethernet, wifi, and Homeplug), and IPtouchscreens. The DeviceConnect is a device abstraction layer thatenables any device or protocol layer to interoperate with integratedsecurity system components. This architecture enables the addition ofnew devices supporting any of these interfaces, as well as add entirelynew protocols.

The benefit of DeviceConnect is that it provides supplier flexibility.The same consistent touchscreen, web, and mobile user experience operateunchanged on whatever security equipment selected by a security systemprovider, with the system provider's choice of IP cameras, backend datacenter and central station software.

The integrated security system provides a complete system thatintegrates or layers on top of a conventional host security systemavailable from a security system provider. The security system providertherefore can select different components or configurations to offer(e.g., CDMA, GPRS, no cellular, etc.) as well as have iControl modifythe integrated security system configuration for the system provider'sspecific needs (e.g., change the functionality of the web or mobileportal, add a GE or Honeywell-compatible TouchScreen, etc.).

The integrated security system integrates with the security systemprovider infrastructure for central station reporting directly viaBroadband and GPRS alarm transmissions. Traditional dial-up reporting issupported via the standard panel connectivity. Additionally, theintegrated security system provides interfaces for advancedfunctionality to the CMS, including enhanced alarm events, systeminstallation optimizations, system test verification, videoverification, 2-way voice over IP and GSM.

The integrated security system is an IP centric system that includesbroadband connectivity so that the gateway augments the existingsecurity system with broadband and GPRS connectivity. If broadband isdown or unavailable GPRS may be used, for example. The integratedsecurity system supports GPRS connectivity using an optional wirelesspackage that includes a GPRS modem in the gateway. The integratedsecurity system treats the GPRS connection as a higher cost thoughflexible option for data transfers. In an embodiment the GPRS connectionis only used to route alarm events (e.g., for cost), however the gatewaycan be configured (e.g., through the iConnect server interface) to actas a primary channel and pass any or all events over GPRS. Consequently,the integrated security system does not interfere with the current plainold telephone service (POTS) security panel interface. Alarm events canstill be routed through POTS; however the gateway also allows suchevents to be routed through a broadband or GPRS connection as well. Theintegrated security system provides a web application interface to theCSR tool suite as well as XML web services interfaces for programmaticintegration between the security system provider's existing call centerproducts. The integrated security system includes, for example, APIsthat allow the security system provider to integrate components of theintegrated security system into a custom call center interface. The APIsinclude XML web service APIs for integration of existing security systemprovider call center applications with the integrated security systemservice. All functionality available in the CSR Web application isprovided with these API sets. The Java and XML-based APIs of theintegrated security system support provisioning, billing, systemadministration, CSR, central station, portal user interfaces, andcontent management functions, to name a few. The integrated securitysystem can provide a customized interface to the security systemprovider's billing system, or alternatively can provide security systemdevelopers with APIs and support in the integration effort.

The integrated security system provides or includes business componentinterfaces for provisioning, administration, and customer care to name afew. Standard templates and examples are provided with a definedcustomer professional services engagement to help integrate OSS/BSSsystems of a Service Provider with the integrated security system.

The integrated security system components support and allow for theintegration of customer account creation and deletion with a securitysystem. The iConnect APIs provides access to the provisioning andaccount management system in iConnect and provide full support foraccount creation, provisioning, and deletion. Depending on therequirements of the security system provider, the iConnect APIs can beused to completely customize any aspect of the integrated securitysystem backend operational system.

The integrated security system includes a gateway that supports thefollowing standards-based interfaces, to name a few: Ethernet IPcommunications via Ethernet ports on the gateway, and standardXML/TCP/IP protocols and ports are employed over secured SSL sessions;USB 2.0 via ports on the gateway; 802.11b/g/n IP communications;GSM/GPRS RF WAN communications; CDMA 1×RTT RF WAN communications(optional, can also support EVDO and 3G technologies).

The gateway supports the following proprietary interfaces, to name afew: interfaces including Dialog RF network (319.5 MHz) and RS485Superbus 2000 wired interface; RF mesh network (908 MHz); and interfacesincluding RF network (345 MHz) and RS485/RS232bus wired interfaces.

Regarding security for the IP communications (e.g., authentication,authorization, encryption, anti-spoofing, etc), the integrated securitysystem uses SSL to encrypt all IP traffic, using server andclient-certificates for authentication, as well as authentication in thedata sent over the SSL-encrypted channel. For encryption, integratedsecurity system issues public/private key pairs at the time/place ofmanufacture, and certificates are not stored in any online storage in anembodiment.

The integrated security system does not need any special rules at thecustomer premise and/or at the security system provider central stationbecause the integrated security system makes outgoing connections usingTCP over the standard HTTP and HTTPS ports. Provided outbound TCPconnections are allowed then no special requirements on the firewallsare necessary.

FIG. 1 is a block diagram of the integrated security system 100, underan embodiment. The integrated security system 100 of an embodimentincludes the gateway 102 and the security servers 104 coupled to theconventional home security system 110. At a customer's home or business,the gateway 102 connects and manages the diverse variety of homesecurity and self-monitoring devices. The gateway 102 communicates withthe iConnect Servers 104 located in the service provider's data center106 (or hosted in integrated security system data center), with thecommunication taking place via a communication network 108 or othernetwork (e.g., cellular network, internet, etc.). These servers 104manage the system integrations necessary to deliver the integratedsystem service described herein. The combination of the gateway 102 andthe iConnect servers 104 enable a wide variety of remote client devices120 (e.g., PCs, mobile phones and PDAs) allowing users to remotely stayin touch with their home, business and family. In addition, thetechnology allows home security and self-monitoring information, as wellas relevant third party content such as traffic and weather, to bepresented in intuitive ways within the home, such as on advancedtouchscreen keypads.

The integrated security system service (also referred to as iControlservice) can be managed by a service provider via browser-basedMaintenance and Service Management applications that are provided withthe iConnect Servers. Or, if desired, the service can be more tightlyintegrated with existing OS SB SS and service delivery systems via theiConnect web services-based XML APIs.

The integrated security system service can also coordinate the sendingof alarms to the home security Central Monitoring Station (CMS) 199.Alarms are passed to the CMS 199 using standard protocols such asContact ID or SIA and can be generated from the home security panellocation as well as by iConnect server 104 conditions (such as lack ofcommunications with the integrated security system). In addition, thelink between the security servers 104 and CMS 199 provides tighterintegration between home security and self-monitoring devices and thegateway 102. Such integration enables advanced security capabilitiessuch as the ability for CMS personnel to view photos taken at the time aburglary alarm was triggered. For maximum security, the gateway 102 andiConnect servers 104 support the use of a mobile network (both GPRS andCDMA options are available) as a backup to the primary broadbandconnection.

The integrated security system service is delivered by hosted serversrunning software components that communicate with a variety of clienttypes while interacting with other systems. FIG. 2 is a block diagram ofcomponents of the integrated security system 100, under an embodiment.Following is a more detailed description of the components.

The iConnect servers 104 support a diverse collection of clients 120ranging from mobile devices, to PCs, to in-home security devices, to aservice provider's internal systems. Most clients 120 are used byend-users, but there are also a number of clients 120 that are used tooperate the service.

Clients 120 used by end-users of the integrated security system 100include, but are not limited to, the following:

-   -   Clients based on gateway client applications 202 (e.g., a        processor-based device running the gateway technology that        manages home security and automation devices).    -   A web browser 204 accessing a Web Portal application, performing        end-user configuration and customization of the integrated        security system service as well as monitoring of in-home device        status, viewing photos and video, etc. Device and user        management can also be performed by this portal application.    -   A mobile device 206 (e.g., PDA, mobile phone, etc.) accessing        the integrated security system Mobile Portal. This type of        client 206 is used by end-users to view system status and        perform operations on devices (e.g., turning on a lamp, arming a        security panel, etc.) rather than for system configuration tasks        such as adding a new device or user.    -   PC or browser-based “widget” containers 208 that present        integrated security system service content, as well as other        third-party content, in simple, targeted ways (e.g. a widget        that resides on a PC desktop and shows live video from a single        in-home camera).    -   Touchscreen home security keypads 208 and advanced in-home        devices that present a variety of content widgets via an        intuitive touchscreen user interface.    -   Notification recipients 210 (e.g., cell phones that receive        SMS-based notifications when certain events occur (or don't        occur), email clients that receive an email message with similar        information, etc.).    -   Custom-built clients (not shown) that access the iConnect web        services XML API to interact with users' home security and        self-monitoring information in new and unique ways. Such clients        could include new types of mobile devices, or complex        applications where integrated security system content is        integrated into a broader set of application features.

In addition to the end-user clients, the iConnect servers 104 support PCbrowser-based Service Management clients that manage the ongoingoperation of the overall service. These clients run applications thathandle tasks such as provisioning, service monitoring, customer supportand reporting.

There are numerous types of server components of the iConnect servers104 of an embodiment including, but not limited to, the following:Business Components which manage information about all of the homesecurity and self-monitoring devices; End-User Application Componentswhich display that information for users and access the BusinessComponents via published XML APIs; and Service Management ApplicationComponents which enable operators to administer the service (thesecomponents also access the Business Components via the XML APIs, andalso via published SNMP MIBs).

The server components provide access to, and management of, the objectsassociated with an integrated security system installation. Thetop-level object is the “network.” It is a location where a gateway 102is located, and is also commonly referred to as a site or premises; thepremises can include any type of structure (e.g., home, office,warehouse, etc.) at which an gateway 102 is located. Users can onlyaccess the networks to which they have been granted permission. Within anetwork, every object monitored by the gateway 102 is called a device.Devices include the sensors, cameras, home security panels andautomation devices, as well as the controller or processor-based devicerunning the gateway applications.

Various types of interactions are possible between the objects in asystem. Automations define actions that occur as a result of a change instate of a device. For example, take a picture with the front entrycamera when the front door sensor changes to “open”. Notifications aremessages sent to users to indicate that something has occurred, such asthe front door going to “open” state, or has not occurred (referred toas an iWatch notification). Schedules define changes in device statesthat are to take place at predefined days and times. For example, setthe security panel to “Armed” mode every weeknight at 11:00 pm.

The iConnect Business Components are responsible for orchestrating allof the low-level service management activities for the integratedsecurity system service. They define all of the users and devicesassociated with a network (site), analyze how the devices interact, andtrigger associated actions (such as sending notifications to users). Allchanges in device states are monitored and logged. The BusinessComponents also manage all interactions with external systems asrequired, including sending alarms and other related self-monitoringdata to the home security Central Monitoring System (CMS) 199. TheBusiness Components are implemented as portable Java J2EE Servlets, butare not so limited.

The following iConnect Business Components manage the main elements ofthe integrated security system service, but the embodiment is not solimited:

-   -   A Registry Manager 220 defines and manages users and networks.        This component is responsible for the creation, modification and        termination of users and networks. It is also where a user's        access to networks is defined.    -   A Network Manager 222 defines and manages security and        self-monitoring devices that are deployed on a network (site).        This component handles the creation, modification, deletion and        configuration of the devices, as well as the creation of        automations, schedules and notification rules associated with        those devices.    -   A Data Manager 224 manages access to current and logged state        data for an existing network and its devices. This component        specifically does not provide any access to network management        capabilities, such as adding new devices to a network, which are        handled exclusively by the Network Manager 222.    -   To achieve optimal performance for all types of queries, data        for current device states is stored separately from historical        state data (a.k.a. “logs”) in the database. A Log Data Manager        226 performs ongoing transfers of current device state data to        the historical data log tables.

Additional iConnect Business Components handle direct communicationswith certain clients and other systems, for example:

-   -   An iHub Manager 228 directly manages all communications with        iHub clients, including receiving information about device state        changes, changing the configuration of devices, and pushing new        versions of the iHub client to the hardware it is running on.    -   A Notification Manager 230 is responsible for sending all        notifications to clients via SMS (mobile phone messages), email        (via a relay server like an SMTP email server), etc.    -   An Alarm and CMS Manager 232 sends critical server-generated        alarm events to the home security Central Monitoring Station        (CMS) and manages all other communications of integrated        security system service data to and from the CMS.    -   The Element Management System (EMS) 234 is an iControl Business        Component that manages all activities associated with service        installation, scaling and monitoring, and filters and packages        service operations data for use by service management        applications. The SNMP MIBs published by the EMS can also be        incorporated into any third party monitoring system if desired.

The iConnect Business Components store information about the objectsthat they manage in the iControl Service Database 240 and in theiControl Content Store 242. The iControl Content Store is used to storemedia objects like video, photos and widget content, while the ServiceDatabase stores information about users, networks, and devices. Databaseinteraction is performed via a JDBC interface. For security purposes,the Business Components manage all data storage and retrieval.

The iControl Business Components provide web services-based APIs thatapplication components use to access the Business Components'capabilities. Functions of application components include presentingintegrated security system service data to end-users, performingadministrative duties, and integrating with external systems andback-office applications.

The primary published APIs for the iConnect Business Components include,but are not limited to, the following:

-   -   A Registry Manager API 252 provides access to the Registry        Manager Business Component's functionality, allowing management        of networks and users.    -   A Network Manager API 254 provides access to the Network Manager        Business Component's functionality, allowing management of        devices on a network.    -   A Data Manager API 256 provides access to the Data Manager        Business Component's functionality, such as setting and        retrieving (current and historical) data about device states.    -   A Provisioning API 258 provides a simple way to create new        networks and configure initial default properties.

Each API of an embodiment includes two modes of access: Java API or XMLAPI. The XML APIs are published as web services so that they can beeasily accessed by applications or servers over a network. The Java APIsare a programmer-friendly wrapper for the XML APIs. Applicationcomponents and integrations written in Java should generally use theJava APIs rather than the XML APIs directly.

The iConnect Business Components also have an XML-based interface 260for quickly adding support for new devices to the integrated securitysystem. This interface 260, referred to as DeviceConnect 260, is aflexible, standards-based mechanism for defining the properties of newdevices and how they can be managed. Although the format is flexibleenough to allow the addition of any type of future device, pre-definedXML profiles are currently available for adding common types of devicessuch as sensors (SensorConnect), home security panels (PanelConnect) andIP cameras (CameraConnect).

The iConnect End-User Application Components deliver the user interfacesthat run on the different types of clients supported by the integratedsecurity system service. The components are written in portable JavaJ2EE technology (e.g., as Java Servlets, as JavaServer Pages (JSPs),etc.) and they all interact with the iControl Business Components viathe published APIs.

The following End-User Application Components generate CSS-basedHTML/JavaScript that is displayed on the target client. Theseapplications can be dynamically branded with partner-specific logos andURL links (such as Customer Support, etc.). The End-User ApplicationComponents of an embodiment include, but are not limited to, thefollowing:

-   -   An iControl Activation Application 270 that delivers the first        application that a user sees when they set up the integrated        security system service. This wizard-based web browser        application securely associates a new user with a purchased        gateway and the other devices included with it as a kit (if        any). It primarily uses functionality published by the        Provisioning API.    -   An iControl Web Portal Application 272 runs on PC browsers and        delivers the web-based interface to the integrated security        system service. This application allows users to manage their        networks (e.g. add devices and create automations) as well as to        view/change device states, and manage pictures and videos.        Because of the wide scope of capabilities of this application,        it uses three different Business Component APIs that include the        Registry Manager API, Network Manager API, and Data Manager API,        but the embodiment is not so limited.    -   An iControl Mobile Portal 274 is a small-footprint web-based        interface that runs on mobile phones and PDAs. This interface is        optimized for remote viewing of device states and        pictures/videos rather than network management. As such, its        interaction with the Business Components is primarily via the        Data Manager API.    -   Custom portals and targeted client applications can be provided        that leverage the same Business Component APIs used by the above        applications.    -   A Content Manager Application Component 276 delivers content to        a variety of clients. It sends multimedia-rich user interface        components to widget container clients (both PC and        browser-based), as well as to advanced touchscreen keypad        clients. In addition to providing content directly to end-user        devices, the Content Manager 276 provides widget-based user        interface components to satisfy requests from other Application        Components such as the iControl Web 272 and Mobile 274 portals.

A number of Application Components are responsible for overallmanagement of the service. These pre-defined applications, referred toas Service Management Application Components, are configured to offeroff-the-shelf solutions for production management of the integratedsecurity system service including provisioning, overall servicemonitoring, customer support, and reporting, for example. The ServiceManagement Application Components of an embodiment include, but are notlimited to, the following:

-   -   A Service Management Application 280 allows service        administrators to perform activities associated with service        installation, scaling and monitoring/alerting. This application        interacts heavily with the Element Management System (EMS)        Business Component to execute its functionality, and also        retrieves its monitoring data from that component via protocols        such as SNMP MIBs.    -   A Kitting Application 282 is used by employees performing        service provisioning tasks. This application allows home        security and self-monitoring devices to be associated with        gateways during the warehouse kitting process.    -   A CSR Application and Report Generator 284 is used by personnel        supporting the integrated security system service, such as CSRs        resolving end-user issues and employees enquiring about overall        service usage. Pushes of new gateway firmware to deployed        gateways is also managed by this application.

The iConnect servers 104 also support custom-built integrations with aservice provider's existing OSS/BSS, CSR and service delivery systems290. Such systems can access the iConnect web services XML API totransfer data to and from the iConnect servers 104. These types ofintegrations can compliment or replace the PC browser-based ServiceManagement applications, depending on service provider needs.

As described above, the integrated security system of an embodimentincludes an gateway, or iHub. The gateway of an embodiment includes adevice that is deployed in the home or business and couples or connectsthe various third-party cameras, home security panels, sensors anddevices to the iConnect server over a WAN connection as described indetail herein. The gateway couples to the home network and communicatesdirectly with the home security panel in both wired and wireless sensorinstallations. The gateway is configured to be low-cost, reliable andthin so that it complements the integrated security system network-basedarchitecture.

The gateway supports various wireless protocols and can interconnectwith a wide range of home security control panels. Service providers andusers can then extend the system's capabilities by adding IP cameras,lighting modules and additional security devices. The gateway isconfigurable to be integrated into many consumer appliances, includingset-top boxes, routers and security panels. The small and efficientfootprint of the gateway enables this portability and versatility,thereby simplifying and reducing the overall cost of the deployment.

FIG. 3 is a block diagram of the gateway 102 including gateway softwareor applications, under an embodiment. The gateway software architectureis relatively thin and efficient, thereby simplifying its integrationinto other consumer appliances such as set-top boxes, routers, touchscreens and security panels. The software architecture also provides ahigh degree of security against unauthorized access. This sectiondescribes the various key components of the gateway softwarearchitecture.

The gateway application layer 302 is the main program that orchestratesthe operations performed by the gateway. The Security Engine 304provides robust protection against intentional and unintentionalintrusion into the integrated security system network from the outsideworld (both from inside the premises as well as from the WAN). TheSecurity Engine 304 of an embodiment comprises one or more sub-modulesor components that perform functions including, but not limited to, thefollowing:

-   -   Encryption including 128-bit SSL encryption for gateway and        iConnect server communication to protect user data privacy and        provide secure communication.    -   Bi-directional authentication between the gateway and iConnect        server in order to prevent unauthorized spoofing and attacks.        Data sent from the iConnect server to the gateway application        (or vice versa) is digitally signed as an additional layer of        security. Digital signing provides both authentication and        validation that the data has not been altered in transit.    -   Camera SSL encapsulation because picture and video traffic        offered by off-the-shelf networked IP cameras is not secure when        traveling over the Internet. The gateway provides for 128-bit        SSL encapsulation of the user picture and video data sent over        the internet for complete user security and privacy.    -   802.11b/g/n with WPA-2 security to ensure that wireless camera        communications always takes place using the strongest available        protection.    -   An gateway-enabled device is assigned a unique activation key        for activation with an iConnect server. This ensures that only        valid gateway-enabled devices can be activated for use with the        specific instance of iConnect server in use. Attempts to        activate gateway-enabled devices by brute force are detected by        the Security Engine. Partners deploying gateway-enabled devices        have the knowledge that only an gateway with the correct serial        number and activation key can be activated for use with an        iConnect server. Stolen devices, devices attempting to        masquerade as gateway-enabled devices, and malicious outsiders        (or insiders as knowledgeable but nefarious customers) cannot        effect other customers' gateway-enabled devices.

As standards evolve, and new encryption and authentication methods areproven to be useful, and older mechanisms proven to be breakable, thesecurity manager can be upgraded “over the air” to provide new andbetter security for communications between the iConnect server and thegateway application, and locally at the premises to remove any risk ofeavesdropping on camera communications.

A Remote Firmware Download module 306 allows for seamless and secureupdates to the gateway firmware through the iControl MaintenanceApplication on the server 104, providing a transparent, hassle-freemechanism for the service provider to deploy new features and bug fixesto the installed user base. The firmware download mechanism is tolerantof connection loss, power interruption and user interventions (bothintentional and unintentional). Such robustness reduces down time andcustomer support issues. Gateway firmware can be remotely downloadeither for one gateway at a time, a group of gateways, or in batches.

The Automations engine 308 manages the user-defined rules of interactionbetween the different devices (e.g. when door opens turn on the light).Though the automation rules are programmed and reside at theportal/server level, they are cached at the gateway level in order toprovide short latency between device triggers and actions.

DeviceConnect 310 includes definitions of all supported devices (e.g.,cameras, security panels, sensors, etc.) using a standardized plug-inarchitecture. The DeviceConnect module 310 offers an interface that canbe used to quickly add support for any new device as well as enablinginteroperability between devices that use differenttechnologies/protocols. For common device types, pre-defined sub-moduleshave been defined, making supporting new devices of these types eveneasier. SensorConnect 312 is provided for adding new sensors,CameraConnect 316 for adding IP cameras, and PanelConnect 314 for addinghome security panels.

The Schedules engine 318 is responsible for executing the user definedschedules (e.g., take a picture every five minutes; every day at 8 amset temperature to 65 degrees Fahrenheit, etc.). Though the schedulesare programmed and reside at the iConnect server level they are sent tothe scheduler within the gateway application. The Schedules Engine 318then interfaces with SensorConnect 312 to ensure that scheduled eventsoccur at precisely the desired time.

The Device Management module 320 is in charge of all discovery,installation and configuration of both wired and wireless IP devices(e.g., cameras, etc.) coupled or connected to the system. Networked IPdevices, such as those used in the integrated security system, requireuser configuration of many IP and security parameters—to simplify theuser experience and reduce the customer support burden, the devicemanagement module of an embodiment handles the details of thisconfiguration. The device management module also manages the videorouting module described below.

The video routing engine 322 is responsible for delivering seamlessvideo streams to the user with zero-configuration. Through a multi-step,staged approach the video routing engine uses a combination of UPnPport-forwarding, relay server routing and STUN/TURN peer-to-peerrouting.

FIG. 4 is a block diagram of components of the gateway 102, under anembodiment. Depending on the specific set of functionality desired bythe service provider deploying the integrated security system service,the gateway 102 can use any of a number of processors 402, due to thesmall footprint of the gateway application firmware. In an embodiment,the gateway could include the Broadcom BCM5354 as the processor forexample. In addition, the gateway 102 includes memory (e.g., FLASH 404,RAM 406, etc.) and any number of input/output (I/O) ports 408.

Referring to the WAN portion 410 of the gateway 102, the gateway 102 ofan embodiment can communicate with the iConnect server using a number ofcommunication types and/or protocols, for example Broadband 412, GPRS414 and/or Public Switched Telephone Network (PTSN) 416 to name a few.In general, broadband communication 412 is the primary means ofconnection between the gateway 102 and the iConnect server 104 and theGPRS/CDMA 414 and/or PSTN 416 interfaces acts as backup for faulttolerance in case the user's broadband connection fails for whateverreason, but the embodiment is not so limited.

Referring to the LAN portion 420 of the gateway 102, various protocolsand physical transceivers can be used to communicate to off-the-shelfsensors and cameras. The gateway 102 is protocol-agnostic andtechnology-agnostic and as such can easily support almost any devicenetworking protocol. The gateway 102 can, for example, support GE andHoneywell security RF protocols 422, Z-Wave 424, serial (RS232 andRS485) 426 for direct connection to security panels as well as WiFi 428(802.11b/g) for communication to WiFi cameras.

The integrated security system includes couplings or connections among avariety of IP devices or components, and the device management module isin charge of the discovery, installation and configuration of the IPdevices coupled or connected to the system, as described above. Theintegrated security system of an embodiment uses a “sandbox” network todiscover and manage all IP devices coupled or connected as components ofthe system. The IP devices of an embodiment include wired devices,wireless devices, cameras, interactive touchscreens, and security panelsto name a few. These devices can be wired via ethernet cable or Wifidevices, all of which are secured within the sandbox network, asdescribed below. The “sandbox” network is described in detail below.

FIG. 5 is a block diagram 500 of network or premise device integrationwith a premise network 250, under an embodiment. In an embodiment,network devices 255-257 are coupled to the gateway 102 using a securenetwork connection such as SSL over an encrypted 802.11 link (utilizingfor example WPA-2 security for the wireless encryption), and the gateway102 is coupled to the premise router/firewall 252 via a coupling with apremise LAN 250. The premise router/firewall 252 is coupled to abroadband modem 251, and the broadband modem 251 is coupled to a WAN 200or other network outside the premise. The gateway 102 thus enables orforms a separate wireless network, or sub-network, that includes somenumber of devices and is coupled or connected to the LAN 250 of the hostpremises. The gateway sub-network can include, but is not limited to,any number of other devices like WiFi IP cameras, security panels (e.g.,IP-enabled), and security touchscreens, to name a few. The gateway 102manages or controls the sub-network separately from the LAN 250 andtransfers data and information between components of the sub-network andthe LAN 250/WAN 200, but is not so limited. Additionally, other networkdevices 254 can be coupled to the LAN 250 without being coupled to thegateway 102.

FIG. 6 is a block diagram 600 of network or premise device integrationwith a premise network 250, under an alternative embodiment. The networkor premise devices 255-257 are coupled to the gateway 102, and thegateway 102 is coupled or connected between the premise router/firewall252 and the broadband modem 251. The broadband modem 251 is coupled to aWAN 200 or other network outside the premise, while the premiserouter/firewall 252 is coupled to a premise LAN 250. As a result of itslocation between the broadband modem 251 and the premise router/firewall252, the gateway 102 can be configured or function as the premise routerrouting specified data between the outside network (e.g., WAN 200) andthe premise router/firewall 252 of the LAN 250. As described above, thegateway 102 in this configuration enables or forms a separate wirelessnetwork, or sub-network, that includes the network or premise devices255-257 and is coupled or connected between the LAN 250 of the hostpremises and the WAN 200. The gateway sub-network can include, but isnot limited to, any number of network or premise devices 255-257 likeWiFi IP cameras, security panels (e.g., IP-enabled), and securitytouchscreens, to name a few. The gateway 102 manages or controls thesub-network separately from the LAN 250 and transfers data andinformation between components of the sub-network and the LAN 250/WAN200, but is not so limited. Additionally, other network devices 254 canbe coupled to the LAN 250 without being coupled to the gateway 102.

The examples described above with reference to FIGS. 5 and 6 arepresented only as examples of IP device integration. The integratedsecurity system is not limited to the type, number and/or combination ofIP devices shown and described in these examples, and any type, numberand/or combination of IP devices is contemplated within the scope ofthis disclosure as capable of being integrated with the premise network.

The integrated security system of an embodiment includes an iControltouchscreen (also referred to as the touchscreen or integrated securitysystem touchscreen), as described above, which provides core securitykeypad functionality, content management and presentation, and embeddedsystems design. The networked security touchscreen system of anembodiment enables a consumer or security provider to easily andautomatically install, configure and manage the security system andtouchscreen located at a customer premise. Using this system thecustomer may access and control the local security system, local IPdevices such as cameras, local sensors and control devices (such aslighting controls or pipe freeze sensors), as well as the local securitysystem panel and associated security sensors (such as door/window,motion, and smoke detectors). The customer premise may be a home,business, and/or other location equipped with a wired or wirelessbroadband IP connection. The system of an embodiment includes atouchscreen with a configurable software user interface, a gatewaydevice (e.g., iHub) that couples or connects to the security panelthrough a wired or wireless connection, a security panel, and a remoteserver that provides access to content and information from the premisesdevices to a user when they are remote from the home. Note that thegateway device may be a separate device or may be physicallyincorporated into the touchscreen.

The touchscreen of an embodiment is integrated into a premise networkusing the gateway, as described above. The gateway as described hereinfunctions to enable a separate wireless network, or sub-network, that iscoupled, connected, or integrated with a network (e.g., WAN, LAN, etc.)of or coupled to the host premises. The sub-network enabled by thegateway optimizes the installation process for IP devices, like thetouchscreen, that couple or connect to the sub-network by segregatingthese IP devices from other such devices on the network. Thissegregation of the IP devices of the sub-network further enablesseparate security and privacy policies to be implemented for these IPdevices so that, where the IP devices are dedicated to specificfunctions (e.g., security), the security and privacy policies can betailored specifically for the specific functions. Furthermore, thegateway and the sub-network it forms enables the segregation of datatraffic, resulting in faster and more efficient data flow betweencomponents of the host network, components of the sub-network, andbetween components of the sub-network and components of the network.

The touchscreen of an embodiment includes a core functional embeddedsystem that includes an embedded operating system, required hardwaredrivers, and an open system interface to name a few. The core functionalembedded system can be provided by or as a component of a conventionalsecurity system (e.g., security system available from GE Security).These core functional units are used with components of the integratedsecurity system as described herein. Note that portions of thetouchscreen description below may include reference to a host premisesecurity system (e.g., GE security system), but these references areincluded only as an example and do not limit the touchscreen tointegration with any particular security system.

As an example, regarding the core functional embedded system, a reducedmemory footprint version of embedded Linux forms the core operatingsystem in an embodiment, and provides basic TCP/IP stack and memorymanagement functions, along with a basic set of low-level graphicsprimitives. A set of device drivers is also provided or included thatoffer low-level hardware and network interfaces. In addition to thestandard drivers, an interface to the RS 485 bus is included thatcouples or connects to the security system panel (e.g., GE Concordpanel). The interface may, for example, implement the Superbus 2000protocol, which can then be utilized by the more comprehensivetransaction-level security functions implemented in PanelConnecttechnology (e.g SetAlarmLevel (int level, int partition,char*accessCode)). Power control drivers are also provided.

FIG. 7 is a block diagram of a touchscreen 700 of the integratedsecurity system, under an embodiment. The touchscreen 700 generallyincludes an application/presentation layer 702 with a residentapplication 704, and a core engine 706. The touchscreen 700 alsoincludes one or more of the following, but is not so limited:applications of premium services 710, widgets 712, a caching proxy 714,network security 716, network interface 718, security object 720,applications supporting devices 722, PanelConnect API 724, a gatewayinterface 726, and one or more ports 728.

More specifically, the touchscreen, when configured as a home securitydevice, includes but is not limited to the following application orsoftware modules: RS 485 and/or RS-232 bus security protocols toconventional home security system panel (e.g., GE Concord panel);functional home security classes and interfaces (e.g. Panel ARM state,Sensor status, etc.); Application/Presentation layer or engine; ResidentApplication; Consumer Home Security Application; installer home securityapplication; core engine; and System bootloader/Software Updater. Thecore Application engine and system bootloader can also be used tosupport other advanced content and applications. This provides aseamless interaction between the premise security application and otheroptional services such as weather widgets or IP cameras.

An alternative configuration of the touchscreen includes a firstApplication engine for premise security and a second Application enginefor all other applications. The integrated security system applicationengine supports content standards such as HTML, XML, Flash, etc. andenables a rich consumer experience for all ‘widgets’, whethersecurity-based or not. The touchscreen thus provides service providersthe ability to use web content creation and management tools to buildand download any ‘widgets’ regardless of their functionality.

As discussed above, although the Security Applications have specificlow-level functional requirements in order to interface with the premisesecurity system, these applications make use of the same fundamentalapplication facilities as any other ‘widget’, application facilitiesthat include graphical layout, interactivity, application handoff,screen management, and network interfaces, to name a few.

Content management in the touchscreen provides the ability to leverageconventional web development tools, performance optimized for anembedded system, service provider control of accessible content, contentreliability in a consumer device, and consistency between ‘widgets’ andseamless widget operational environment. In an embodiment of theintegrated security system, widgets are created by web developers andhosted on the integrated security system Content Manager (and stored inthe Content Store database). In this embodiment the server componentcaches the widgets and offers them to consumers through the web-basedintegrated security system provisioning system. The servers interactwith the advanced touchscreen using HTTPS interfaces controlled by thecore engine and dynamically download widgets and updates as needed to becached on the touchscreen. In other embodiments widgets can be accesseddirectly over a network such as the Internet without needing to gothrough the iControl Content Manager

Referring to FIG. 7, the touchscreen system is built on a tieredarchitecture, with defined interfaces between theApplication/Presentation Layer (the Application Engine) on the top, theCore Engine in the middle, and the security panel and gateway APIs atthe lower level. The architecture is configured to provide maximumflexibility and ease of maintenance.

The application engine of the touchscreen provides the presentation andinteractivity capabilities for all applications (widgets) that run onthe touchscreen, including both core security function widgets and thirdparty content widgets. A fundamental component of the application engineis the Presentation Engine, which includes a set of libraries thatimplement the standards-based widget content (e.g., XML, HTML,JavaScript, Flash) layout and interactivity. This engine provides thewidget with interfaces to dynamically load both graphics and applicationlogic from third parties, support high level data description languageas well as standard graphic formats. The set of web content-basedfunctionality available to a widget developer is extended by specifictouchscreen functions implemented as local web services by the CoreEngine.

The resident application of the touchscreen is the master service thatcontrols the interaction of all widgets (all applications in thesystem), and enforces the business and security rules required by theservice provider. For example, the resident application determines thepriority of widgets, thereby enabling a home security widget to overrideresource requests from a less critical widget (e.g. a weather widget).The resident application also monitors widget behavior, and responds toclient or server requests for cache updates.

The core engine of the touchscreen manages interaction with othercomponents of the integrated security system, and provides an interfacethrough which the resident application and authorized widgets can getinformation about the home security system, set alarms, install sensors,etc. At the lower level, the Core Engine's main interactions are throughthe PanelConnect API, which handles all communication with the securitypanel, and the gateway Interface, which handles communication with thegateway. In an embodiment, both the iHub Interface and PanelConnect APIare resident and operating on the touchscreen. In another embodiment,the PanelConnect API runs on the gateway or other device that providessecurity system interaction and is accessed by the touchscreen through aweb services interface.

The Core Engine also handles application and service level persistentand cached memory functions, as well as the dynamic provisioning ofcontent and widgets, including but not limited to: flash memorymanagement, local widget and content caching, widget version management(download, cache flush new/old content versions), as well as the cachingand synchronization of user preferences. As a portion of these servicesthe Core engine incorporates the bootloader functionality that isresponsible for maintaining a consistent software image on thetouchscreen, and acts as the client agent for all software updates. Thebootloader is configured to ensure full update redundancy so thatunsuccessful downloads cannot corrupt the integrated security system.

Video management is provided as a set of web services by the CoreEngine. Video management includes the retrieval and playback of localvideo feeds as well as remote control and management of cameras (allthrough iControl CameraConnect technology).

Both the high level application layer and the mid-level core engine ofthe touchscreen can make calls to the network. Any call to the networkmade by the application layer is automatically handed off to a localcaching proxy, which determines whether the request should be handledlocally. Many of the requests from the application layer are webservices API requests; although such requests could be satisfied by theiControl servers, they are handled directly by the touchscreen and thegateway. Requests that get through the caching proxy are checked againsta white list of acceptable sites, and, if they match, are sent offthrough the network interface to the gateway. Included in the NetworkSubsystem is a set of network services including HTTP, HTTPS, andserver-level authentication functions to manage the secure client-serverinterface. Storage and management of certificates is incorporated as apart of the network services layer.

Server components of the integrated security system servers supportinteractive content services on the touchscreen. These server componentsinclude, but are not limited to the content manager, registry manager,network manager, and global registry, each of which is described herein.

The Content Manager oversees aspects of handling widget data and rawcontent on the touchscreen. Once created and validated by the serviceprovider, widgets are ‘ingested’ to the Content Manager, and then becomeavailable as downloadable services through the integrated securitysystem Content Management APIs. The Content manager maintains versionsand timestamp information, and connects to the raw data contained in thebackend Content Store database. When a widget is updated (or new contentbecomes available) all clients registering interest in a widget aresystematically updated as needed (a process that can be configured at anaccount, locale, or system-wide level).

The Registry Manager handles user data, and provisioning accounts,including information about widgets the user has decided to install, andthe user preferences for these widgets.

The Network Manager handles getting and setting state for all devices onthe integrated security system network (e.g., sensors, panels, cameras,etc.). The Network manager synchronizes with the gateway, the advancedtouchscreen, and the subscriber database.

The Global Registry is a primary starting point server for all clientservices, and is a logical referral service that abstracts specificserver locations/addresses from clients (touchscreen, gateway 102,desktop widgets, etc.). This approach enables easy scaling/migration ofserver farms.

The gateway 102 of an embodiment, as described herein, enables couplingsor connections and thus the flow of information between variouscomponents of the host premises and various types and/or combinations ofIP devices, where the components of the host premises include a network,a security system or subsystem to name a few. Consequently, the gateway102 controls the association between and the flow of information or databetween the components of the host premises. For example, the gateway102 of an embodiment forms a sub-network coupled to another network(e.g., WAN, LAN, etc.), with the sub-network including IP devices. Thegateway further enables the association of the IP devices of thesub-network with appropriate systems on the premises (e.g., securitysystem, etc.). Therefore, for example, the gateway can form asub-network of IP devices configured for security functions, andassociate the sub-network only with the premises security system,thereby segregating the IP devices dedicated to security from other IPdevices that may be coupled to another network on the premises.

FIG. 8 is a flow diagram for a method 800 of forming a security networkincluding integrated security system components, under an embodiment.Generally, the method comprises coupling 802 a gateway comprising aconnection management component to a local area network in a firstlocation and a security server in a second location. The methodcomprises forming 804 a security network by automatically establishing awireless coupling between the gateway and a security system using theconnection management component. The security system of an embodimentcomprises security system components located at the first location. Themethod comprises integrating 806 communications and functions of thesecurity system components into the security network via the wirelesscoupling.

FIG. 9 is a flow diagram for a method 900 of forming a security networkincluding integrated security system components and network devices,under an embodiment. Generally, the method comprises coupling 902 agateway to a local area network located in a first location and asecurity server in a second location. The method comprises automaticallyestablishing 904 communications between the gateway and security systemcomponents at the first location, the security system including thesecurity system components. The method comprises automaticallyestablishing 906 communications between the gateway and premise devicesat the first location. The method comprises forming 908 a securitynetwork by electronically integrating, via the gateway, communicationsand functions of the premise devices and the security system components.

In an example embodiment, FIG. 10 is a flow diagram 1000 for integrationor installation of an IP device into a private network environment,under an embodiment. The variables of an embodiment set at time ofinstallation include, but are not limited to, one or more of a privateSSID/Password, an gateway identifier, a security panel identifier, auser account TS, and a Central Monitoring Station accountidentification.

An embodiment of the IP device discovery and management begins with auser or installer activating 1002 the gateway and initiating 1004 theinstall mode of the system. This places the gateway in an install mode.Once in install mode, the gateway shifts to a default (Install) Wificonfiguration. This setting will match the default setting for otherintegrated security system-enabled devices that have been pre-configuredto work with the integrated security system. The gateway will then beginto provide 1006 DHCP addresses for these IP devices. Once the deviceshave acquired a new DHCP address from the gateway, those devices areavailable for configuration into a new secured Wifi network setting.

The user or installer of the system selects 1008 all devices that havebeen identified as available for inclusion into the integrated securitysystem. The user may select these devices by their unique IDs via a webpage, Touchscreen, or other client interface. The gateway provides 1010data as appropriate to the devices. Once selected, the devices areconfigured 1012 with appropriate secured Wifi settings, including SSIDand WPA/WPA-2 keys that are used once the gateway switches back to thesecured sandbox configuration from the “Install” settings. Othersettings are also configured as appropriate for that type of device.Once all devices have been configured, the user is notified and the usercan exit install mode. At this point all devices will have beenregistered 1014 with the integrated security system servers.

The installer switches 1016 the gateway to an operational mode, and thegateway instructs or directs 1018 all newly configured devices to switchto the “secured” Wifi sandbox settings. The gateway then switches 1020to the “secured” Wifi settings. Once the devices identify that thegateway is active on the “secured” network, they request new DHCPaddresses from the gateway which, in response, provides 1022 the newaddresses. The devices with the new addresses are then operational 1024on the secured network.

In order to ensure the highest level of security on the secured network,the gateway can create or generate a dynamic network securityconfiguration based on the unique ID and private key in the gateway,coupled with a randomizing factor that can be based on online time orother inputs. This guarantees the uniqueness of the gateway securednetwork configuration.

To enable the highest level of performance, the gateway analyzes the RFspectrum of the 802.11x network and determines which frequencyband/channel it should select to run.

An alternative embodiment of the camera/IP device management processleverages the local ethernet connection of the sandbox network on thegateway. This alternative process is similar to the Wifi discoveryembodiment described above, except the user connects the targeted deviceto the ethernet port of the sandbox network to begin the process. Thisalternative embodiment accommodates devices that have not beenpre-configured with the default “Install” configuration for theintegrated security system.

This alternative embodiment of the IP device discovery and managementbegins with the user/installer placing the system into install mode. Theuser is instructed to attach an IP device to be installed to the sandboxethernet port of the gateway. The IP device requests a DHCP address fromthe gateway which, in response to the request, provides the address. Theuser is presented the device and is asked if he/she wants to install thedevice. If yes, the system configures the device with the secured Wifisettings and other device-specific settings (e.g., camera settings forvideo length, image quality etc.). The user is next instructed todisconnect the device from the ethernet port. The device is nowavailable for use on the secured sandbox network.

FIG. 11 is a block diagram showing communications among integrated IPdevices of the private network environment, under an embodiment. The IPdevices of this example include a security touchscreen 1103, gateway1102 (e.g., “iHub”), and security panel (e.g., “Security Panel 1”,“Security Panel 2”, “Security Panel n”), but the embodiment is not solimited. In alternative embodiments any number and/or combination ofthese three primary component types may be combined with othercomponents including IP devices and/or security system components. Forexample, a single device which comprises an integrated gateway,touchscreen, and security panel is merely another embodiment of theintegrated security system described herein. The description thatfollows includes an example configuration that includes a touchscreenhosting particular applications. However, the embodiment is not limitedto the touchscreen hosting these applications, and the touchscreenshould be thought of as representing any IP device.

Referring to FIG. 11, the touchscreen 1103 incorporates an application1110 that is implemented as computer code resident on the touchscreenoperating system, or as a web-based application running in a browser, oras another type of scripted application (e.g., Flash, Java, VisualBasic, etc.). The touchscreen core application 1110 represents thisapplication, providing user interface and logic for the end user tomanage their security system or to gain access to networked informationor content (Widgets). The touchscreen core application 1110 in turnaccesses a library or libraries of functions to control the localhardware (e.g. screen display, sound, LEDs, memory, etc.) as well asspecialized librarie(s) to couple or connect to the security system.

In an embodiment of this security system connection, the touchscreen1103 communicates to the gateway 1102, and has no direct communicationwith the security panel. In this embodiment, the touchscreen coreapplication 1110 accesses the remote service APIs 1112 which providesecurity system functionality (e.g. ARM/DISARM panel, sensor state,get/set panel configuration parameters, initiate or get alarm events,etc.). In an embodiment, the remote service APIs 1112 implement one ormore of the following functions, but the embodiment is not so limited:

-   -   Armstate=setARMState(type=“ARM STAY|ARM AWAY|DISARM”,        Parameters=“ExitDelay=30|Lights=OFF”)    -   sensorState=getSensors(type=“ALL|SensorName|SensorNameList”)    -   result=setSensorState(SensorName, parameters=“Option1, Options2,        . . . Option n”)    -   interruptHandler=SensorEvent( )    -   interruptHandler=alarmEvent( )

Functions of the remote service APIs 1112 of an embodiment use a remotePanelConnect API 1124 which resides in memory on the gateway 1102. Thetouchscreen 1103 communicates with the gateway 1102 through a suitablenetwork interface such as an Ethernet or 802.11 RF connection, forexample. The remote PanelConnect API 1124 provides the underlyingSecurity System Interfaces 1126 used to communicate with and control oneor more types of security panel via wired link 1130 and/or RF link 3.The PanelConnect API 1124 provides responses and input to the remoteservices APIs 1126, and in turn translates function calls and data toand from the specific protocols and functions supported by a specificimplementation of a Security Panel (e.g. a GE Security Simon XT orHoneywell Vista 20P). In an embodiment, the PanelConnect API 1124 uses a345 MHz RF transceiver or receiver hardware/firmware module tocommunicate wirelessly to the security panel and directly to a set of345 MHz RF-enabled sensors and devices, but the embodiment is not solimited.

The gateway of an alternative embodiment communicates over a wiredphysical coupling or connection to the security panel using the panel'sspecific wired hardware (bus) interface and the panel's bus-levelprotocol.

In an alternative embodiment, the Touchscreen 1103 implements the samePanelConnect API 1114 locally on the Touchscreen 1103, communicatingdirectly with the Security Panel 2 and/or Sensors 2 over the proprietaryRF link or over a wired link for that system. In this embodiment theTouchscreen 1103, instead of the gateway 1102, incorporates the 345 MHzRF transceiver to communicate directly with Security Panel 2 or Sensors2 over the RF link 2. In the case of a wired link the Touchscreen 1103incorporates the real-time hardware (e.g. a PIC chip and RS232-variantserial link) to physically connect to and satisfy the specific bus-leveltiming requirements of the SecurityPanel2.

In yet another alternative embodiment, either the gateway 1102 or theTouchscreen 1103 implements the remote service APIs. This embodimentincludes a Cricket device (“Cricket”) which comprises but is not limitedto the following components: a processor (suitable for handling 802.11protocols and processing, as well as the bus timing requirements ofSecurityPanel1); an 802.11 (WiFi) client IP interface chip; and, aserial bus interface chip that implements variants of RS232 or RS485,depending on the specific Security Panel.

The Cricket also implements the full PanelConnect APIs such that it canperform the same functions as the case where the gateway implements thePanelConnect APIs. In this embodiment, the touchscreen core application1110 calls functions in the remote service APIs 1112 (such assetArmState( )). These functions in turn couple or connect to the remoteCricket through a standard IP connection (“Cricket IP Link”) (e.g.,Ethernet, Homeplug, the gateway's proprietary Wifi network, etc.). TheCricket in turn implements the PanelConnect API, which responds to therequest from the touchscreen core application, and performs theappropriate function using the proprietary panel interface. Thisinterface uses either the wireless or wired proprietary protocol for thespecific security panel and/or sensors.

FIG. 12 is a flow diagram of a method of integrating an external controland management application system with an existing security system,under an embodiment. Operations begin when the system is powered on1210, involving at a minimum the power-on of the gateway device, andoptionally the power-on of the connection between the gateway device andthe remote servers. The gateway device initiates 1220 a software and RFsequence to locate the extant security system. The gateway and installerinitiate and complete 1230 a sequence to ‘learn’ the gateway into thesecurity system as a valid and authorized control device. The gatewayinitiates 1240 another software and RF sequence of instructions todiscover and learn the existence and capabilities of existing RF deviceswithin the extant security system, and store this information in thesystem. These operations under the system of an embodiment are describedin further detail below.

Unlike conventional systems that extend an existing security system, thesystem of an embodiment operates utilizing the proprietary wirelessprotocols of the security system manufacturer. In one illustrativeembodiment, the gateway is an embedded computer with an IP LAN and WANconnection and a plurality of RF transceivers and software protocolmodules capable of communicating with a plurality of security systemseach with a potentially different RF and software protocol interface.After the gateway has completed the discovery and learning 1240 ofsensors and has been integrated 1250 as a virtual control device in theextant security system, the system becomes operational. Thus, thesecurity system and associated sensors are presented 1250 as accessibledevices to a potential plurality of user interface subsystems.

The system of an embodiment integrates 1260 the functionality of theextant security system with other non-security devices including but notlimited to IP cameras, touchscreens, lighting controls, door lockingmechanisms, which may be controlled via RF, wired, or powerline-basednetworking mechanisms supported by the gateway or servers.

The system of an embodiment provides a user interface subsystem 1270enabling a user to monitor, manage, and control the system andassociated sensors and security systems. In an embodiment of the system,a user interface subsystem is an HTML/XML/Javascript/Java/AJAX/Flashpresentation of a monitoring and control application, enabling users toview the state of all sensors and controllers in the extant securitysystem from a web browser or equivalent operating on a computer, PDA,mobile phone, or other consumer device.

In another illustrative embodiment of the system described herein, auser interface subsystem is an HTML/XML/Javascript/Java/AJAXpresentation of a monitoring and control application, enabling users tocombine the monitoring and control of the extant security system andsensors with the monitoring and control of non-security devicesincluding but not limited to IP cameras, touchscreens, lightingcontrols, door locking mechanisms.

In another illustrative embodiment of the system described herein, auser interface subsystem is a mobile phone application enabling users tomonitor and control the extant security system as well as othernon-security devices.

In another illustrative embodiment of the system described herein, auser interface subsystem is an application running on a keypad ortouchscreen device enabling users to monitor and control the extantsecurity system as well as other non-security devices.

In another illustrative embodiment of the system described herein, auser interface subsystem is an application operating on a TV or set-topbox connected to a TV enabling users to monitor and control the extantsecurity system as well as other non-security devices.

FIG. 13 is a block diagram of an integrated security system 1300wirelessly interfacing to proprietary security systems, under anembodiment. A security system 1310 is coupled or connected to a Gateway1320, and from Gateway 1320 coupled or connected to a plurality ofinformation and content sources across a network 1330 including one ormore web servers 1340, system databases 1350, and applications servers1360. While in one embodiment network 1330 is the Internet, includingthe World Wide Web, those of skill in the art will appreciate thatnetwork 1330 may be any type of network, such as an intranet, anextranet, a virtual private network (VPN), a mobile network, or anon-TCP/IP based network.

Moreover, other elements of the system of an embodiment may beconventional, well-known elements that need not be explained in detailherein. For example, security system 1310 could be any type home orbusiness security system, such devices including but not limited to astandalone RF home security system or a non-RF-capable wired homesecurity system with an add-on RF interface module. In the example ofFIG. 13, security system 1310 includes an RF-capable wireless securitypanel (WSP) 1311 that acts as the master controller for security system1310. Well-known examples of such a WSP include the GE Security Concord,Networx, and Simon panels, the Honeywell Vista and Lynx panels, andsimilar panels from DSC and Napco, to name a few. A wireless module 1314includes the RF hardware and protocol software necessary to enablecommunication with and control of a plurality of wireless devices 1313.WSP 1311 may also manage wired devices 1314 physically connected to WSP1311 with an RS232 or RS485 or Ethernet connection or similar such wiredinterface.

In an implementation consistent with the systems and methods describedherein, Gateway 1320 provides the interface between security system 1310and LAN and/or WAN for purposes of remote control, monitoring, andmanagement. Gateway 1320 communicates with an external web server 1340,database 1350, and application server 1360 over network 1330 (which maycomprise WAN, LAN, or a combination thereof). In this example system,application logic, remote user interface functionality, as well as userstate and account are managed by the combination of these remoteservers. Gateway 1320 includes server connection manager 1321, asoftware interface module responsible for all server communication overnetwork 1330. Event manager 1322 implements the main event loop forGateway 1320, processing events received from device manager 1324(communicating with non-security system devices including but notlimited to IP cameras, wireless thermostats, or remote door locks).Event manager 1322 further processes events and control messages fromand to security system 1310 by utilizing WSP manager 1323.

WSP manager 1323 and device manager 1324 both rely upon wirelessprotocol manager 1326 which receives and stores the proprietary orstandards-based protocols required to support security system 1310 aswell as any other devices interfacing with gateway 1320. WSP manager1323 further utilizes the comprehensive protocols and interfacealgorithms for a plurality of security systems 1310 stored in the WSP DBclient database associated with wireless protocol manager 1326. Thesevarious components implement the software logic and protocols necessaryto communicate with and manager devices and security systems 1310.Wireless Transceiver hardware modules 1325 are then used to implementthe physical RF communications link to such devices and security systems1310. An illustrative wireless transceiver 1325 is the GE SecurityDialog circuit board, implementing a 319.5 MHz two-way RF transceivermodule. In this example, RF Link 1370 represents the 319.5 MHz RFcommunication link, enabling gateway 1320 to monitor and control WSP1311 and associated wireless and wired devices 1313 and 1314,respectively.

In one embodiment, server connection manager 1321 requests and receivesa set of wireless protocols for a specific security system 1310 (anillustrative example being that of the GE Security Concord panel andsensors) and stores them in the WSP DB portion of the wireless protocolmanager 1326. WSP manager 1323 then utilizes such protocols fromwireless protocol manager 1326 to initiate the sequence of processesdetailed in FIG. 12 and FIG. 13 for learning gateway 1320 into securitysystem 1310 as an authorized control device. Once learned in, asdescribed with reference to FIG. 13 (and above), event manager 1322processes all events and messages detected by the combination of WSPmanager 1323 and the GE Security wireless transceiver module 1325.

In another embodiment, gateway 1320 incorporates a plurality of wirelesstransceivers 1325 and associated protocols managed by wireless protocolmanager 1326. In this embodiment events and control of multipleheterogeneous devices may be coordinated with WSP 1311, wireless devices1313, and wired devices 1314. For example a wireless sensor from onemanufacturer may be utilized to control a device using a differentprotocol from a different manufacturer.

In another embodiment, gateway 1320 incorporates a wired interface tosecurity system 1310, and incorporates a plurality of wirelesstransceivers 1325 and associated protocols managed by wireless protocolmanager 1326. In this embodiment events and control of multipleheterogeneous devices may be coordinated with WSP 1311, wireless devices1313, and wired devices 1314.

Of course, while an illustrative embodiment of an architecture of thesystem of an embodiment is described in detail herein with respect toFIG. 13, one of skill in the art will understand that modifications tothis architecture may be made without departing from the scope of thedescription presented herein. For example, the functionality describedherein may be allocated differently between client and server, oramongst different server or processor-based components. Likewise, theentire functionality of the gateway 1320 described herein could beintegrated completely within an existing security system 1310. In suchan embodiment, the architecture could be directly integrated with asecurity system 1310 in a manner consistent with the currently describedembodiments.

FIG. 14 is a flow diagram for wirelessly ‘learning’ the Gateway into anexisting security system and discovering extant sensors, under anembodiment. The learning interfaces gateway 1320 with security system1310. Gateway 1320 powers up 1410 and initiates software sequences 1420and 1425 to identify accessible WSPs 1311 and wireless devices 1313,respectively (e.g., one or more WSPs and/or devices within range ofgateway 1320). Once identified, WSP 1311 is manually or automaticallyset into ‘learn mode’ 1430, and gateway 1320 utilizes availableprotocols to add 1440 itself as an authorized control device in securitysystem 1310. Upon successful completion of this task, WSP 1311 ismanually or automatically removed from ‘learn mode’ 1450.

Gateway 1320 utilizes the appropriate protocols to mimic 1460 the firstidentified device 1314. In this operation gateway 1320 identifies itselfusing the unique or pseudo-unique identifier of the first found device1314, and sends an appropriate change of state message over RF Link1370. In the event that WSP 1311 responds to this change of statemessage, the device 1314 is then added 1470 to the system in database1350. Gateway 1320 associates 1480 any other information (such as zonename or token-based identifier) with this device 1314 in database 1350,enabling gateway 1320, user interface modules, or any application toretrieve this associated information.

In the event that WSP 1311 does not respond to the change of statemessage, the device 1314 is not added 1470 to the system in database1350, and this device 1314 is identified as not being a part of securitysystem 1310 with a flag, and is either ignored or added as anindependent device, at the discretion of the system provisioning rules.Operations hereunder repeat 1485 operations 1460, 1470, 1480 for alldevices 1314 if applicable. Once all devices 1314 have been tested inthis way, the system begins operation 1490.

In another embodiment, gateway 1320 utilizes a wired connection to WSP1311, but also incorporates a wireless transceiver 1325 to communicatedirectly with devices 1314. In this embodiment, operations under 1420above are removed, and operations under 1440 above are modified so thesystem of this embodiment utilizes wireline protocols to add itself asan authorized control device in security system 1310.

A description of an example embodiment follows in which the Gateway(FIG. 13, element 1320) is the iHub available from iControl Networks,Palo Alto, Calif., and described in detail herein. In this example thegateway is “automatically” installed with a security system.

The automatic security system installation begins with the assignment ofan authorization key to components of the security system (e.g.,gateway, kit including the gateway, etc.). The assignment of anauthorization key is done in lieu of creating a user account. Aninstaller later places the gateway in a user's premises along with thepremises security system. The installer uses a computer to navigate to aweb portal (e.g., integrated security system web interface), logs in tothe portal, and enters the authorization key of the installed gatewayinto the web portal for authentication. Once authenticated, the gatewayautomatically discovers devices at the premises (e.g., sensors, cameras,light controls, etc.) and adds the discovered devices to the system or“network”. The installer assigns names to the devices, and testsoperation of the devices back to the server (e.g., did the door open,did the camera take a picture, etc.). The security device information isoptionally pushed or otherwise propagated to a security panel and/or tothe server network database. The installer finishes the installation,and instructs the end user on how to create an account, username, andpassword. At this time the user enters the authorization key whichvalidates the account creation (uses a valid authorization key toassociate the network with the user's account). New devices maysubsequently be added to the security network in a variety of ways(e.g., user first enters a unique ID for each device/sensor and names itin the server, after which the gateway can automatically discover andconfigure the device).

A description of another example embodiment follows in which thesecurity system (FIG. 13, element 1310) is a Dialog system and the WSP(FIG. 13, element 1311) is a SimonXT available from General ElectricSecurity, and the Gateway (FIG. 13, element 1320) is the iHub availablefrom iControl Networks, Palo Alto, Calif., and described in detailherein. Descriptions of the install process for the SimonXT and iHub arealso provided below.

GE Security's Dialog network is one of the most widely deployed andtested wireless security systems in the world. The physical RF networkis based on a 319.5 MHz unlicensed spectrum, with a bandwidth supportingup to 19 Kbps communications. Typical use of this bandwidth—even inconjunction with the integrated security system—is far less than that.Devices on this network can support either one-way communication (eithera transmitter or a receiver) or two-way communication (a transceiver).Certain GE Simon, Simon XT, and Concord security control panelsincorporate a two-way transceiver as a standard component. The gatewayalso incorporates the same two-way transceiver card. The physical linklayer of the network is managed by the transceiver module hardware andfirmware, while the coded payload bitstreams are made available to theapplication layer for processing.

Sensors in the Dialog network typically use a 60-bit protocol forcommunicating with the security panel transceiver, while security systemkeypads and the gateway use the encrypted 80-bit protocol. The Dialognetwork is configured for reliability, as well as low-power usage. Manydevices are supervised, i.e. they are regularly monitored by the system‘master’ (typically a GE security panel), while still maintainingexcellent power usage characteristics. A typical door window sensor hasa battery life in excess of 5-7 years.

The gateway has two modes of operation in the Dialog network: a firstmode of operation is when the gateway is configured or operates as a‘slave’ to the GE security panel; a second mode of operation is when thegateway is configured or operates as a ‘master’ to the system in theevent a security panel is not present. In both configurations, thegateway has the ability to ‘listen’ to network traffic, enabling thegateway to continually keep track of the status of all devices in thesystem. Similarly, in both situations the gateway can address andcontrol devices that support setting adjustments (such as the GEwireless thermostat).

In the configuration in which the gateway acts as a ‘slave’ to thesecurity panel, the gateway is ‘learned into’ the system as a GEwireless keypad. In this mode of operation, the gateway emulates asecurity system keypad when managing the security panel, and can querythe security panel for status and ‘listen’ to security panel events(such as alarm events).

The gateway incorporates an RF Transceiver manufactured by GE Security,but is not so limited. This transceiver implements the Dialog protocolsand handles all network message transmissions, receptions, and timing.As such, the physical, link, and protocol layers of the communicationsbetween the gateway and any GE device in the Dialog network are totallycompliant with GE Security specifications.

At the application level, the gateway emulates the behavior of a GEwireless keypad utilizing the GE Security 80-bit encrypted protocol, andonly supported protocols and network traffic are generated by thegateway. Extensions to the Dialog RF protocol of an embodiment enablefull control and configuration of the panel, and iControl can bothautomate installation and sensor enrollment as well as directconfiguration downloads for the panel under these protocol extensions.

As described above, the gateway participates in the GE Security networkat the customer premises. Because the gateway has intelligence and atwo-way transceiver, it can ‘hear’ all of the traffic on that network.The gateway makes use of the periodic sensor updates, state changes, andsupervisory signals of the network to maintain a current state of thepremises. This data is relayed to the integrated security system server(e.g., FIG. 2, element 260) and stored in the event repository for useby other server components. This usage of the GE Security RF network iscompletely non-invasive; there is no new data traffic created to supportthis activity.

The gateway can directly (or indirectly through the Simon XT panel)control two-way devices on the network. For example, the gateway candirect a GE Security Thermostat to change its setting to ‘Cool’ from‘Off’, as well as request an update on the current temperature of theroom. The gateway performs these functions using the existing GE Dialogprotocols, with little to no impact on the network; a gateway devicecontrol or data request takes only a few dozen bytes of data in anetwork that can support 19 Kbps.

By enrolling with the Simon XT as a wireless keypad, as describedherein, the gateway includes data or information of all alarm events, aswell as state changes relevant to the security panel. This informationis transferred to the gateway as encrypted packets in the same way thatthe information is transferred to all other wireless keypads on thenetwork.

Because of its status as an authorized keypad, the gateway can alsoinitiate the same panel commands that a keypad can initiate. Forexample, the gateway can arm or disarm the panel using the standardDialog protocol for this activity. Other than the monitoring of standardalarm events like other network keypads, the only incremental datatraffic on the network as a result of the gateway is the infrequentremote arm/disarm events that the gateway initiates, or infrequentqueries on the state of the panel.

The gateway is enrolled into the Simon XT panel as a ‘slave’ devicewhich, in an embodiment, is a wireless keypad. This enables the gatewayfor all necessary functionality for operating the Simon XT systemremotely, as well as combining the actions and information ofnon-security devices such as lighting or door locks with GE Securitydevices. The only resource taken up by the gateway in this scenario isone wireless zone (sensor ID).

The gateway of an embodiment supports three forms of sensor and panelenrollment/installation into the integrated security system, but is notlimited to this number of enrollment/installation options. Theenrollment/installation options of an embodiment include installerinstallation, kitting, and panel, each of which is described below.

Under the installer option, the installer enters the sensor IDs at timeof installation into the integrated security system web portal oriScreen. This technique is supported in all configurations andinstallations.

Kits can be pre-provisioned using integrated security systemprovisioning applications when using the kitting option. At kittingtime, multiple sensors are automatically associated with an account, andat install time there is no additional work required.

In the case where a panel is installed with sensors already enrolled(i.e. using the GE Simon XT enrollment process), the gateway has thecapability to automatically extract the sensor information from thesystem and incorporate it into the user account on the integratedsecurity system server.

The gateway and integrated security system of an embodiment uses anauto-learn process for sensor and panel enrollment in an embodiment. Thedeployment approach of an embodiment can use additional interfaces thatGE Security is adding to the Simon XT panel. With these interfaces, thegateway has the capability to remotely enroll sensors in the panelautomatically. The interfaces include, but are not limited to, thefollowing: EnrollDevice(ID, type, name, zone, group);SetDeviceParameters(ID, type, Name, zone, group),GetDeviceParameters(zone); and RemoveDevice(zone).

The integrated security system incorporates these new interfaces intothe system, providing the following install process. The install processcan include integrated security system logistics to handle kitting andpre-provisioning. Pre-kitting and logistics can include apre-provisioning kitting tool provided by integrated security systemthat enables a security system vendor or provider (“provider”) to offerpre-packaged initial ‘kits’. This is not required but is recommended forsimplifying the install process. This example assumes a ‘Basic’ kit ispreassembled and includes one (1) Simon XT, three (3) Door/windowsensors, one (1) motion sensor, one (1) gateway, one (1) keyfob, two (2)cameras, and ethernet cables. The kit also includes a sticker page withall Zones (1-24) and Names (full name list).

The provider uses the integrated security system kitting tool toassemble ‘Basic’ kit packages. The contents of different types ofstarter kits may be defined by the provider. At the distributionwarehouse, a worker uses a bar code scanner to scan each sensor and thegateway as it is packed into the box. An ID label is created that isattached to the box. The scanning process automatically associates allthe devices with one kit, and the new ID label is the unique identifierof the kit. These boxes are then sent to the provider for distributionto installer warehouses. Individual sensors, cameras, etc. are also sentto the provider installer warehouse. Each is labeled with its ownbarcode/ID.

An installation and enrollment procedure of a security system includingan gateway is described below as one example of the installationprocess.

-   1. Order and Physical Install Process    -   a. Once an order is generated in the iControl system, an account        is created and an install ticket is created and sent        electronically to the provider for assignment to an installer.    -   b. The assigned installer picks up his/her ticket(s) and fills        his/her truck with Basic and/or Advanced starter kits. He/she        also keeps a stock of individual sensors, cameras, iHubs, Simon        XTs, etc. Optionally, the installer can also stock homeplug        adapters for problematic installations.    -   c. The installer arrives at the address on the ticket, and pulls        out the Basic kit. The installer determines sensor locations        from a tour of the premises and discussion with the homeowner.        At this point assume the homeowner requests additional equipment        including an extra camera, two (2) additional door/window        sensors, one (1) glass break detector, and one (1) smoke        detector.    -   d. Installer mounts SimonXT in the kitchen or other location in        the home as directed by the homeowner, and routes the phone line        to Simon XT if available. GPRS and Phone numbers pre-programmed        in SimonXT to point to the provider Central Monitoring Station        (CMS).    -   e. Installer places iHub in the home in the vicinity of a router        and cable modem. Installer installs an ethernet line from iHub        to router and plugs iHub into an electrical outlet.-   2. Associate and Enroll iHub into SimonXT    -   a. Installer uses either his/her own laptop plugged into router,        or homeowners computer to go to the integrated security system        web interface and log in with installer ID/pass.    -   b. Installer enters ticket number into admin interface, and        clicks ‘New Install’ button. Screen prompts installer for kit ID        (on box's barcode label).    -   c. Installer clicks ‘Add SimonXT’. Instructions prompt installer        to put Simon XT into install mode, and add iHub as a wireless        keypad. It is noted that this step is for security only and can        be automated in an embodiment.    -   d. Installer enters the installer code into the Simon XT.        Installer Learns ‘iHub’ into the panel as a wireless keypad as a        group 1 device.    -   e. Installer goes back to Web portal, and clicks the ‘Finished        Adding SimonXT’ button.-   3. Enroll Sensors into SimonXT via iControl    -   a. All devices in the Basic kit are already associated with the        user's account.    -   b. For additional devices, Installer clicks ‘Add Device’ and        adds the additional camera to the user's account (by typing in        the camera ID/Serial #).    -   c. Installer clicks ‘Add Device’ and adds other sensors (two (2)        door/window sensors, one (1) glass break sensor, and one (1)        smoke sensor) to the account (e.g., by typing in IDs).    -   d. As part of Add Device, Installer assigns zone, name, and        group to the sensor. Installer puts appropriate Zone and Name        sticker on the sensor temporarily.    -   e. All sensor information for the account is pushed or otherwise        propagated to the iConnect server, and is available to propagate        to CMS automation software through the CMS application        programming interface (API).    -   f. Web interface displays ‘Installing Sensors in System . . . ’        and automatically adds all of the sensors to the Simon XT panel        through the GE RF link.    -   g. Web interface displays ‘Done Installing’→all sensors show        green.-   4. Place and Tests Sensors in Home    -   a. Installer physically mounts each sensor in its desired        location, and removes the stickers.    -   b. Installer physically mounts WiFi cameras in their location        and plugs into AC power. Optional fishing of low voltage wire        through wall to remove dangling wires. Camera transformer is        still plugged into outlet but wire is now inside the wall.    -   c. Installer goes to Web interface and is prompted for automatic        camera install. Each camera is provisioned as a private,        encrypted Wifi device on the iHub secured sandbox network, and        firewall NAT traversal is initiated. Upon completion the        customer is prompted to test the security system.    -   d. Installer selects the ‘Test System’ button on the web        portal—the SimonXT is put into Test mode by the iHub over GE RF.    -   e. Installer manually tests the operation of each sensor,        receiving an audible confirmation from SimonXT.    -   f. iHub sends test data directly to CMS over broadband link, as        well as storing the test data in the user's account for        subsequent report generation.    -   g. Installer exits test mode from the Web portal.-   5. Installer instructs customer on use of the Simon XT, and shows    customer how to log into the iControl web and mobile portals.    Customer creates a username/password at this time.-   6. Installer instructs customer how to change Simon XT user code    from the Web interface. Customer changes user code which is pushed    to SimonXT automatically over GE RF.

An installation and enrollment procedure of a security system includingan gateway is described below as an alternative example of theinstallation process. This installation process is for use for enrollingsensors into the SimonXT and integrated security system and iscompatible with all existing GE Simon panels.

The integrated security system supports all pre-kitting functionalitydescribed in the installation process above. However, for the purpose ofthe following example, no kitting is used.

-   -   1. Order and Physical Install Process        -   a. Once an order is generated in the iControl system, an            account is created and an install ticket is created and sent            electronically to the security system provider for            assignment to an installer.        -   b. The assigned installer picks up his/her ticket(s) and            fills his/her truck with individual sensors, cameras, iHubs,            Simon XTs, etc. Optionally, the installer can also stock            homeplug adapters for problematic installations.        -   c. The installer arrives at the address on the ticket, and            analyzes the house and talks with the homeowner to determine            sensor locations. At this point assume the homeowner            requests three (3) cameras, five (5) door/window sensors,            one (1) glass break detector, one (1) smoke detector, and            one (1) keyfob.        -   d. Installer mounts SimonXT in the kitchen or other location            in the home. The installer routes a phone line to Simon XT            if available. GPRS and Phone numbers are pre-programmed in            SimonXT to point to the provider CMS.        -   e. Installer places iHub in home in the vicinity of a router            and cable modem, and installs an ethernet line from iHub to            the router, and plugs iHub into an electrical outlet.    -   2. Associate and Enroll iHub into SimonXT        -   a. Installer uses either his/her own laptop plugged into            router, or homeowners computer to go to the integrated            security system web interface and log in with an installer            ID/pass.        -   b. Installer enters ticket number into admin interface, and            clicks ‘New Install’ button. Screen prompts installer to add            devices.        -   c. Installer types in ID of iHub, and it is associated with            the user's account.        -   d. Installer clicks ‘Add Device’ and adds the cameras to the            user's account (by typing in the camera ID/Serial #).        -   e. Installer clicks ‘Add SimonXT’. Instructions prompt            installer to put Simon XT into install mode, and add iHub as            a wireless keypad.        -   f. Installer goes to Simon XT and enters the installer code            into the Simon XT. Learns ‘iHub’ into the panel as a            wireless keypad as group 1 type sensor.        -   g. Installer returns to Web portal, and clicks the ‘Finished            Adding SimonXT’ button.        -   h. iHub now is alerted to all subsequent installs over the            security system RF.    -   3. Enroll Sensors into SimonXT via iControl        -   a. Installer clicks ‘Add Simon XT Sensors’—Displays            instructions for adding sensors to Simon XT.        -   b. Installer goes to Simon XT and uses Simon XT install            process to add each sensor, assigning zone, name, group.            These assignments are recorded for later use.        -   c. The iHub automatically detects each sensor addition and            adds the new sensor to the integrated security system.        -   d. Installer exits install mode on the Simon XT, and returns            to the Web portal.        -   e. Installer clicks ‘Done Adding Devices’.        -   f. Installer enters zone/sensor naming from recorded notes            into integrated security system to associate sensors to            friendly names.        -   g. All sensor information for the account is pushed to the            iConnect server, and is available to propagate to CMS            automation software through the CMS API.    -   4. Place and Tests Sensors in Home        -   a. Installer physically mounts each sensor in its desired            location.        -   b. Installer physically mounts Wifi cameras in their            location and plugs into AC power. Optional fishing of low            voltage wire through wall to remove dangling wires. Camera            transformer is still plugged into outlet but wire is now            inside the wall.        -   c. Installer puts SimonXT into Test mode from the keypad.        -   d. Installer manually tests the operation of each sensor,            receiving an audible confirmation from SimonXT.        -   e. Installer exits test mode from the Simon XT keypad.        -   f. Installer returns to web interface and is prompted to            automatically set up cameras. After waiting for completion            cameras are now provisioned and operational.    -   5. Installer instructs customer on use of the Simon XT, and        shows customer how to log into the integrated security system        web and mobile portals. Customer creates a username/password at        this time.    -   6. Customer and Installer observe that all sensors/cameras are        green.    -   7. Installer instructs customer how to change Simon XT user code        from the keypad. Customer changes user code and stores in        SimonXT.    -   8. The first time the customer uses the web portal to Arm/Disarm        system the web interface prompts the customer for the user code,        which is then stored securely on the server. In the event the        user code is changed on the panel the web interface once again        prompts the customer.

The panel of an embodiment can be programmed remotely. The CMS pushesnew programming to SimonXT over a telephone or GPRS link. Optionally,iControl and GE provide a broadband link or coupling to the gateway andthen a link from the gateway to the Simon XT over GE RF.

As described above, computer networks suitable for use with theembodiments described herein include local area networks (LAN), widearea networks (WAN), Internet, or other connection services and networkvariations such as the world wide web, the public internet, a privateinternet, a private computer network, a public network, a mobilenetwork, a cellular network, a value-added network, and the like.Computing devices coupled or connected to the network may be anymicroprocessor controlled device that permits access to the network,including terminal devices, such as personal computers, workstations,servers, mini computers, main-frame computers, laptop computers, mobilecomputers, palm top computers, hand held computers, mobile phones, TVset-top boxes, or combinations thereof. The computer network may includeone of more LANs, WANs, Internets, and computers. The computers mayserve as servers, clients, or a combination thereof.

The integrated security system can be a component of a single system,multiple systems, and/or geographically separate systems. The integratedsecurity system can also be a subcomponent or subsystem of a singlesystem, multiple systems, and/or geographically separate systems. Theintegrated security system can be coupled to one or more othercomponents (not shown) of a host system or a system coupled to the hostsystem.

One or more components of the integrated security system and/or acorresponding system or application to which the integrated securitysystem is coupled or connected includes and/or runs under and/or inassociation with a processing system. The processing system includes anycollection of processor-based devices or computing devices operatingtogether, or components of processing systems or devices, as is known inthe art. For example, the processing system can include one or more of aportable computer, portable communication device operating in acommunication network, and/or a network server. The portable computercan be any of a number and/or combination of devices selected from amongpersonal computers, personal digital assistants, portable computingdevices, and portable communication devices, but is not so limited. Theprocessing system can include components within a larger computersystem.

The processing system of an embodiment includes at least one processorand at least one memory device or subsystem. The processing system canalso include or be coupled to at least one database. The term“processor” as generally used herein refers to any logic processingunit, such as one or more central processing units (CPUs), digitalsignal processors (DSPs), application-specific integrated circuits(ASIC), etc. The processor and memory can be monolithically integratedonto a single chip, distributed among a number of chips or components,and/or provided by some combination of algorithms. The methods describedherein can be implemented in one or more of software algorithm(s),programs, firmware, hardware, components, circuitry, in any combination.

The components of any system that includes the integrated securitysystem can be located together or in separate locations. Communicationpaths couple the components and include any medium for communicating ortransferring files among the components. The communication paths includewireless connections, wired connections, and hybrid wireless/wiredconnections. The communication paths also include couplings orconnections to networks including local area networks (LANs),metropolitan area networks (MANs), wide area networks (WANs),proprietary networks, interoffice or backend networks, and the Internet.Furthermore, the communication paths include removable fixed mediumslike floppy disks, hard disk drives, and CD-ROM disks, as well as flashRAM, Universal Serial Bus (USB) connections, RS-232 connections,telephone lines, buses, and electronic mail messages.

Embodiments of the integrated security system include a systemcomprising: a gateway located at a first location; a connectionmanagement component coupled to the gateway, the connection managementcomponent automatically establishing a wireless coupling with a securitysystem installed at the first location, the security system includingsecurity system components, wherein the connection management componentforms a security network that integrates communications and functions ofthe security system components into the security network via thewireless coupling; and a security server at a second location differentfrom the first location, wherein security server is coupled to thegateway.

The gateway of an embodiment is connected to a local area network at thefirst location, and the local area network is coupled to a wide areanetwork via a router at the first location.

The gateway of an embodiment is coupled to a wide area network and iscoupled to a local area network at the first location via the connectionmanagement component and a router at the first location.

The gateway of an embodiment is coupled to the security server via theinternet.

The system of an embodiment comprises an interface coupled to thesecurity network, wherein the interface allows control of the functionsof the security network by a user.

The system of an embodiment comprises a portal coupled to the gateway,wherein the portal provides access to the communications and thefunctions of the security network via remote client devices.

The system of an embodiment comprises an interface coupled to thesecurity network, wherein the interface allows control of the functionsof the security network from the remote client devices.

The remote client devices of an embodiment include one or more ofpersonal computers, personal digital assistants, cellular telephones,and mobile computing devices.

The gateway of an embodiment including the connection managementcomponent automatically discovers the security system components.

The gateway of an embodiment includes protocols of the security systemfrom the security server and uses the protocols to discover the securitysystem components.

The gateway of an embodiment requests and receives protocols of thesecurity system from the security server, wherein the gateway uses theprotocols received to discover the security system components.

The gateway of an embodiment including the connection managementcomponent automatically establishes and controls the communications withthe security system components.

The gateway of an embodiment including the connection managementcomponent automatically establishes a coupling with the security systemincluding the security system components.

The gateway of an embodiment includes a rules component that managesrules of interaction between the gateway and the security systemcomponents.

The gateway of an embodiment includes a device connect component thatincludes definitions of the security system components.

The security system of an embodiment is coupled to a central monitoringstation via a primary communication link, wherein the gateway is coupledto the central monitoring station via a secondary communication linkthat is different than the primary communication link, wherein thecentral monitoring station is located at a third location different fromthe first location and the second location.

The gateway of an embodiment transmits event data of the security systemcomponents to the central monitoring station over the secondarycommunication link.

The event data of an embodiment comprises changes in device states ofthe security system components, data of the security system components,and data received by the security system components.

The secondary communication link of an embodiment includes a broadbandcoupling.

The secondary communication link of an embodiment includes a GeneralPacket Radio Service (GPRS) coupling.

The gateway of an embodiment transmits messages comprising event data ofthe security system components to remote client devices over thesecondary communication link.

The event data of an embodiment comprises changes in device states ofthe security system components, data of the security system components,and data received by the security system components.

The gateway of an embodiment receives control data for control of thesecurity system components from remote client devices via the secondarycommunication link.

The security network of an embodiment comprises network devices coupledto the gateway via a wireless coupling.

The gateway of an embodiment including the connection managementcomponent automatically discovers the network devices.

The gateway of an embodiment including the connection managementcomponent automatically installs the network devices in the securitynetwork.

The gateway of an embodiment including the connection managementcomponent automatically configures the network devices for operation inthe security network.

The gateway of an embodiment controls communications between the networkdevices, the security system components, and the security server.

The gateway of an embodiment including the connection managementcomponent transmits event data of the network devices to remote clientdevices over at least one of a plurality of communication links.

The gateway of an embodiment receives control data for control of thenetwork devices from remote client devices via at least one of theplurality of communication links.

The event data of an embodiment comprises changes in device states ofthe network devices, data of the network devices, and data received bythe network devices.

The security system of an embodiment is coupled to a central monitoringstation via a primary communication link, wherein the gateway is coupledto the central monitoring station via a secondary communication linkthat is different than the primary communication link.

The gateway of an embodiment transmits event data of the network devicesto the central monitoring station over the secondary communication link.

The secondary communication link of an embodiment includes a broadbandcoupling.

The secondary communication link of an embodiment includes a GeneralPacket Radio Service (GPRS) coupling.

The gateway of an embodiment transmits messages comprising event data ofthe network devices to remote client devices over the secondarycommunication link.

The security server of an embodiment creates, modifies and terminatescouplings between the gateway and the network devices.

The security server of an embodiment performs creation, modification,deletion and configuration of the network devices.

The security server of an embodiment creates automations, schedules andnotification rules associated with the network devices.

The security server of an embodiment manages access to current andlogged state data for the network devices.

The security server of an embodiment manages access to current andlogged state data for couplings between the gateway and the networkdevices.

The security server of an embodiment manages communications with thenetwork devices.

The network device of an embodiment is an Internet Protocol device.

The network device of an embodiment is a camera.

The network device of an embodiment is a touchscreen.

The network device of an embodiment is a device controller that controlsan attached device.

The network device of an embodiment is a sensor.

The security server of an embodiment creates, modifies and terminatesusers corresponding to the security system.

The security server of an embodiment creates, modifies and terminatescouplings between the gateway and the security system components.

The security server of an embodiment performs creation, modification,deletion and configuration of the security system components.

The security server of an embodiment creates automations, schedules andnotification rules associated with the security system components.

The security server of an embodiment manages access to current andlogged state data for the security system components.

The security server of an embodiment manages access to current andlogged state data for couplings between the gateway and the securitysystem components.

The security server of an embodiment manages communications with thesecurity system components.

The security server of an embodiment generates and transfersnotifications to remote client devices, the notifications comprisingevent data.

The notifications of an embodiment include one or more of short messageservice messages and electronic mail messages.

The event data of an embodiment is event data of the security systemcomponents.

The security server of an embodiment transmits event data of thesecurity system components to a central monitoring station of thesecurity system over the secondary communication link.

The security system components of an embodiment include one or more ofsensors, cameras, input/output (I/O) devices, and accessory controllers.

Embodiments of the integrated security system include a security networkcomprising: a gateway including a connection management componentlocated at a first location, the connection management componentautomatically establishing a wireless coupling with a security systeminstalled at the first location, the security system including securitysystem components, wherein the connection management component forms asecurity network that integrates communications and functions of thesecurity system components into the security network via the wirelesscoupling; and a security server at a second location different from thefirst location, wherein security server is coupled to the gateway andincludes a plurality of security network applications.

Embodiments of the integrated security system include a security networkcomprising: a gateway including a connection management componentlocated at a first location; a wireless coupling between the gateway anda security system installed at the first location, wherein the securitysystem includes a plurality of security system components that areproprietary to the security system, the connection management componentautomatically establishing the wireless coupling with the securitysystem components and forming a security network that integratescommunications and functions of the security system components into thesecurity network; and an interface coupled to the gateway, the interfaceproviding communications with the security network and control of thefunctions of the security network from a remote client device.

Embodiments of the integrated security system include a systemcomprising: a security network comprising a gateway coupled to asecurity system and located at a first location, the security systemincluding a plurality of security system components, the securitynetwork comprising a plurality of premise devices coupled to thegateway, wherein the gateway electronically integrates communicationsand functions of the plurality of premise devices and the securitysystem components; and a security server located at a second locationdifferent from the first location, the security server coupled to thesecurity network via the gateway.

The system of an embodiment comprises an interface coupled to thesecurity network, wherein the interface allows control of the functionsof the security network by a user.

The system of an embodiment comprises a portal coupled to the gateway,wherein the portal provides access to the communications and thefunctions of the security network via remote client devices.

The system of an embodiment comprises an interface coupled to thesecurity network, wherein the interface allows control of the functionsof the security network from the remote client devices.

The remote client devices of an embodiment include one or more ofpersonal computers, personal digital assistants, cellular telephones,and mobile computing devices.

The gateway of an embodiment automatically discovers the security systemcomponents.

The gateway of an embodiment includes protocols of the security systemfrom the security server and uses the protocols to discover the securitysystem components.

The gateway of an embodiment requests and receives protocols of thesecurity system from the security server, wherein the gateway uses theprotocols received to discover the security system components.

The gateway of an embodiment automatically establishes thecommunications with the security system components.

The gateway of an embodiment includes a connection management component,the connection management component automatically establishing acoupling with the security system including the security systemcomponents.

The connection management component of an embodiment automaticallydiscovers the premise devices.

The connection management component of an embodiment automaticallyinstalls the premise devices in the security network.

The connection management component of an embodiment automaticallyconfigures the premise devices for operation in the security network.

The gateway of an embodiment includes a rules component that managesrules of interaction between the gateway, the security systemcomponents, and the premise devices.

The gateway of an embodiment includes a device connect component thatincludes definitions of the security system components and the premisedevices.

The gateway of an embodiment is connected to a premise local areanetwork, and the premise local area network is coupled to a wide areanetwork via a premise router/firewall.

The gateway of an embodiment is coupled to premise local area networkvia a premise router/firewall, and the gateway is coupled to a wide areanetwork.

The gateway of an embodiment is coupled to the premise devices using awireless coupling.

The gateway of an embodiment is coupled to the security server via theinternet.

The gateway of an embodiment is coupled to a central monitoring stationcorresponding to the security system, wherein the central monitoringstation is located at a third location different from the first locationand the second location.

The security system of an embodiment is coupled to a central monitoringstation via a primary communication link, wherein the gateway is coupledto the central monitoring station via a secondary communication linkthat is different than the primary communication link.

The gateway of an embodiment transmits event data of the security systemcomponents and the premise devices to the central monitoring stationover the secondary communication link.

The event data of an embodiment comprises changes in device states of atleast one of security system components and premise devices, data of atleast one of security system components and premise devices, and datareceived by at least one of security system components and premisedevices.

The gateway of an embodiment transmits event data of the security systemto the central monitoring station over the secondary communication linkwhen the primary communication link is unavailable.

The secondary communication link of an embodiment includes a broadbandcoupling.

The secondary communication link of an embodiment includes a GeneralPacket Radio Service (GPRS) coupling.

The gateway of an embodiment transmits messages comprising event data ofthe security system components and the premise devices to remote clientdevices over the secondary communication link.

The event data of an embodiment comprises changes in device states of atleast one of security system components and premise devices, data of atleast one of security system components and premise devices, and datareceived by at least one of security system components and premisedevices.

The security server of an embodiment creates, modifies and terminatesusers corresponding to the security system.

The security server of an embodiment creates, modifies and terminatescouplings between the gateway and the security system components.

The security server of an embodiment creates, modifies and terminatescouplings between the gateway and the premise devices.

The security server of an embodiment performs creation, modification,deletion and configuration of the security system components.

The security server of an embodiment performs creation, modification,deletion and configuration of the premise devices.

The security server of an embodiment creates automations, schedules andnotification rules associated with the security system components.

The security server of an embodiment creates automations, schedules andnotification rules associated with the premise devices.

The security server of an embodiment manages access to current andlogged state data for the security system components.

The security server of an embodiment manages access to current andlogged state data for the premise devices.

The security server of an embodiment manages access to current andlogged state data for couplings among the gateway, the security systemcomponents and the IP devices.

The security server of an embodiment manages communications with thesecurity system components.

The security server of an embodiment manages communications with thepremise devices.

The security server of an embodiment generates and transfersnotifications to remote client devices, the notifications comprisingevent data.

The notifications of an embodiment include one or more of short messageservice messages and electronic mail messages.

The event data of an embodiment is event data of the security systemcomponents.

The event data of an embodiment is event data of the premise devices.

The security server of an embodiment transmits event data of thesecurity system components and the premise devices to a centralmonitoring station of the security system over the secondarycommunication link.

The security system components of an embodiment include one or more ofsensors, cameras, input/output (I/O) devices, and accessory controllers.

The premise device of an embodiment is an Internet Protocol device.

The premise device of an embodiment is a camera.

The premise device of an embodiment is a touchscreen.

The premise device of an embodiment is a device controller that controlsan attached device.

The premise device of an embodiment is a sensor.

Embodiments of the integrated security system include a systemcomprising: a security network comprising a gateway coupled to asecurity server, wherein the gateway is located at a first location andcoupled to a security system, the security system including securitysystem components located at the first location, wherein the securityserver is located at a second location different from the firstlocation; and a plurality of premise devices located at the firstlocation and coupled to the gateway, wherein the gateway electronicallyintegrates communications and functions of the plurality of premisedevices and the security system components into the security network.

Embodiments of the integrated security system include a security networkcomprising: a gateway, wherein the gateway is coupled to a securitysystem that includes a plurality of security system components that areproprietary to the security system; a plurality of network devicescoupled to the gateway, wherein the gateway forms a premise securitynetwork at a first location and couples the premise security network toa local area network of the first location, wherein the gateway formsthe premise security network by electronically integratingcommunications and functions of the plurality of network devices and thesecurity system components; and an application server located at asecond location different from the first location, the applicationserver coupled to the premise security network via the gateway and acommunication network.

Embodiments of the integrated security system include a systemcomprising: a security network comprising a gateway coupled to asecurity server, wherein the gateway is located at a first location andcoupled to a security system, the security system including securitysystem components located at the first location, wherein the securityserver is located at a second location different from the firstlocation; a plurality of premise devices located at the first locationand coupled to the gateway, wherein the gateway electronicallyintegrates communications and functions of the plurality of premisedevices and the security system components into the security network;and an interface coupled to the gateway, the interface providingcommunications with the security network and control of the functions ofthe security system components and the premise devices from a remoteclient device.

Embodiments of the integrated security system include a methodcomprising: coupling a gateway comprising a connection managementcomponent to a local area network located in a first location and asecurity server in a second location; and forming a security network byautomatically establishing a wireless coupling between the gateway and asecurity system using the connection management component, the securitysystem comprising a plurality of security system components located atthe first location, wherein forming the security network includesintegrating communications and functions of the security systemcomponents into the security network via the wireless coupling.

The method of an embodiment comprises coupling the gateway to a localarea network at the first location, wherein the local area network iscoupled to a wide area network via a router at the first location.

The gateway of an embodiment is coupled to a wide area network and iscoupled to a local area network at the first location via the connectionmanagement component and a router at the first location.

The gateway of an embodiment is coupled to the security server via theinternet.

The method of an embodiment comprises providing an interface of thesecurity network, wherein the interface allows control of the functionsof the security network by a user.

The method of an embodiment comprises providing access to thecommunications and the functions of the security network via remoteclient devices and a portal coupled to the gateway.

The method of an embodiment comprises providing an interface coupled tothe security network, wherein the interface allows control of thefunctions of the security network from the remote client devices.

The remote client devices of an embodiment include one or more ofpersonal computers, personal digital assistants, cellular telephones,and mobile computing devices.

The gateway of an embodiment automatically discovers the security systemcomponents.

The method of an embodiment comprises using protocols of the securitysystem to discover the security system components, wherein the gatewayincludes the protocols.

The method of an embodiment comprises requesting and receiving protocolsof the security system from the security server, wherein the gatewayreceives and uses the protocols to discover the security systemcomponents.

The method of an embodiment comprises automatically establishing andcontrolling the communications with the security system components usingthe gateway.

The gateway of an embodiment including the connection managementcomponent automatically establishes a coupling with the security systemincluding the security system components.

The gateway of an embodiment includes a rules component that managesrules of interaction between the gateway and the security systemcomponents.

The gateway of an embodiment includes a device connect component thatincludes definitions of the security system components.

The security system of an embodiment is coupled to a central monitoringstation via a primary communication link, wherein the gateway is coupledto the central monitoring station via a secondary communication linkthat is different than the primary communication link, wherein thecentral monitoring station is located at a third location different fromthe first location and the second location.

The method of an embodiment comprises transmitting event data of thesecurity system components from the gateway to the central monitoringstation over the secondary communication link.

The event data of an embodiment comprises changes in device states ofthe security system components, data of the security system components,and data received by the security system components.

The secondary communication link of an embodiment includes a broadbandcoupling.

The secondary communication link of an embodiment includes a GeneralPacket Radio Service (GPRS) coupling.

The gateway of an embodiment transmits messages comprising event data ofthe security system components to remote client devices over thesecondary communication link.

The event data of an embodiment comprises changes in device states ofthe security system components, data of the security system components,and data received by the security system components.

The gateway of an embodiment receives control data for control of thesecurity system components from remote client devices via the secondarycommunication link.

The security network of an embodiment comprises network devices coupledto the gateway via a wireless coupling.

The gateway of an embodiment including the connection managementcomponent automatically discovers the network devices.

The gateway of an embodiment including the connection managementcomponent automatically installs the network devices in the securitynetwork.

The gateway of an embodiment including the connection managementcomponent automatically configures the network devices for operation inthe security network.

The gateway of an embodiment controls communications between the networkdevices, the security system components, and the security server.

The gateway of an embodiment including the connection managementcomponent transmits event data of the network devices to remote clientdevices over at least one of a plurality of communication links.

The gateway of an embodiment receives control data for control of thenetwork devices from remote client devices via at least one of theplurality of communication links.

The event data of an embodiment comprises changes in device states ofthe network devices, data of the network devices, and data received bythe network devices.

The security system of an embodiment is coupled to a central monitoringstation via a primary communication link, wherein the gateway is coupledto the central monitoring station via a secondary communication linkthat is different than the primary communication link.

The gateway of an embodiment transmits event data of the network devicesto the central monitoring station over the secondary communication link.

The secondary communication link of an embodiment includes a broadbandcoupling.

The secondary communication link of an embodiment includes a GeneralPacket Radio Service (GPRS) coupling.

The gateway of an embodiment transmits messages comprising event data ofthe network devices to remote client devices over the secondarycommunication link.

The security server of an embodiment creates, modifies and terminatescouplings between the gateway and the network devices.

The security server of an embodiment performs creation, modification,deletion and configuration of the network devices.

The security server of an embodiment creates automations, schedules andnotification rules associated with the network devices.

The security server of an embodiment manages access to current andlogged state data for the network devices.

The security server of an embodiment manages access to current andlogged state data for couplings between the gateway and the networkdevices.

The security server of an embodiment manages communications with thenetwork devices.

The network device of an embodiment is an Internet Protocol device.

The network device of an embodiment is a camera.

The network device of an embodiment is a touchscreen.

The network device of an embodiment is a device controller that controlsan attached device.

The network device of an embodiment is a sensor.

The security server of an embodiment creates, modifies and terminatesusers corresponding to the security system.

The security server of an embodiment creates, modifies and terminatescouplings between the gateway and the security system components.

The security server of an embodiment performs creation, modification,deletion and configuration of the security system components.

The security server of an embodiment creates automations, schedules andnotification rules associated with the security system components.

The security server of an embodiment manages access to current andlogged state data for the security system components.

The security server of an embodiment manages access to current andlogged state data for couplings between the gateway and the securitysystem components.

The security server of an embodiment manages communications with thesecurity system components.

The security server of an embodiment generates and transfersnotifications to remote client devices, the notifications comprisingevent data.

The notifications of an embodiment include one or more of short messageservice messages and electronic mail messages.

The event data of an embodiment is event data of the security systemcomponents.

The security server of an embodiment transmits event data of thesecurity system components to a central monitoring station of thesecurity system over the secondary communication link.

The security system components of an embodiment include one or more ofsensors, cameras, input/output (I/O) devices, and accessory controllers.

Embodiments of the integrated security system include a methodcomprising: coupling a gateway comprising a connection managementcomponent to a local area network located at a facility; and forming asecurity network by automatically establishing a wireless couplingbetween the gateway and a security system using the connectionmanagement component, the security system comprising a plurality ofsecurity system components located at the facility, wherein forming thesecurity network includes integrating communications and functions ofthe security system components into the security network via thewireless coupling.

Embodiments of the integrated security system include a methodcomprising: forming a security network, the forming includingautomatically establishing a wireless coupling between a gateway and asecurity system installed at a facility, wherein the security systemincludes a plurality of security system components that are proprietaryto the security system, the forming including the gateway automaticallyintegrating communications and functions of the security systemcomponents into a local area network of the facility; and providing aninterface by which a remote client device accesses the security network,the interface enabling communications with and control of the functionsof the security system.

Embodiments of the integrated security system include a methodcomprising: coupling a gateway to a local area network located in afirst location and a security server in a second location, wherein thefirst location includes a security system comprising a plurality ofsecurity system components; automatically establishing communicationsbetween the gateway and the security system components; automaticallyestablishing communications between the gateway and premise devices; andforming a security network by electronically integrating, via thegateway, communications and functions of the plurality of premisedevices and the security system components.

The method of an embodiment comprises controlling the functions of thesecurity network via an interface coupled to the security network,wherein the interface is accessed using a remote client device.

The remote client devices of an embodiment include one or more ofpersonal computers, personal digital assistants, cellular telephones,and mobile computing devices.

The method of an embodiment comprises the gateway automaticallydiscovering the security system components.

The method of an embodiment comprises using protocols of the securitysystem to discover the security system components, wherein the gatewayincludes the protocols of the security system.

The method of an embodiment comprises the gateway receiving protocols ofthe security system from the security server in response to a request,wherein the gateway uses the protocols received to discover the securitysystem components.

The gateway of an embodiment comprises a connection managementcomponent, the connection management component automaticallyestablishing a coupling with the security system including the securitysystem components.

The connection management component of an embodiment automaticallydiscovers the premise devices.

The connection management component of an embodiment automaticallyinstalls the premise devices in the security network.

The connection management component of an embodiment automaticallyconfigures the premise devices for operation in the security network.

The gateway of an embodiment includes a rules component that managesrules of interaction between the gateway, the security systemcomponents, and the premise devices.

The gateway of an embodiment includes a device connect component thatincludes definitions of the security system components and the premisedevices.

The premise local area network of an embodiment is coupled to a widearea network via a premise router.

The gateway of an embodiment is coupled to the local area network usinga premise router, and the gateway is coupled to a wide area network.

The gateway of an embodiment is coupled to the premise devices using awireless coupling.

The gateway of an embodiment is coupled to the security server via theinternet.

The gateway of an embodiment is coupled to a central monitoring stationcorresponding to the security system, wherein the central monitoringstation is located at a third location different from the first locationand the second location.

The security system of an embodiment is coupled to a central monitoringstation via a primary communication link, wherein the gateway is coupledto the central monitoring station via a secondary communication linkthat is different than the primary communication link.

The method of an embodiment comprises transmitting event data of thesecurity system components and the premise devices to the centralmonitoring station via the gateway and the secondary communication link.

The event data of an embodiment comprises changes in device states of atleast one of security system components and premise devices, data of atleast one of security system components and premise devices, and datareceived by at least one of security system components and premisedevices.

The method of an embodiment comprises transmitting event data of thesecurity system to the central monitoring station via the gateway andthe secondary communication link when the primary communication link isunavailable.

The secondary communication link of an embodiment includes a broadbandcoupling.

The secondary communication link of an embodiment includes a GeneralPacket Radio Service (GPRS) coupling.

The method of an embodiment comprises transmitting messages comprisingevent data of the security system components and the premise devices toremote client devices via the gateway and the secondary communicationlink.

The event data of an embodiment comprises changes in device states of atleast one of security system components and premise devices, data of atleast one of security system components and premise devices, and datareceived by at least one of security system components and premisedevices.

The security server of an embodiment creates, modifies and terminatesusers corresponding to the security system.

The security server of an embodiment creates, modifies and terminatescouplings between the gateway and the security system components.

The security server of an embodiment creates, modifies and terminatescouplings between the gateway and the premise devices.

The security server of an embodiment performs creation, modification,deletion and configuration of the security system components.

The security server of an embodiment performs creation, modification,deletion and configuration of the premise devices.

The security server of an embodiment creates automations, schedules andnotification rules associated with the security system components.

The security server of an embodiment creates automations, schedules andnotification rules associated with the premise devices.

The security server of an embodiment manages access to current andlogged state data for the security system components.

The security server of an embodiment manages access to current andlogged state data for the premise devices.

The security server of an embodiment manages access to current andlogged state data for couplings among the gateway, the security systemcomponents and the IP devices.

The security server of an embodiment manages communications with thesecurity system components.

The security server of an embodiment manages communications with thepremise devices.

The security server of an embodiment generates and transfersnotifications to remote client devices, the notifications comprisingevent data.

The notifications of an embodiment include one or more of short messageservice messages and electronic mail messages.

The event data of an embodiment is event data of the security systemcomponents.

The event data of an embodiment is event data of the premise devices.

The security server of an embodiment transmits event data of thesecurity system components and the premise devices to a centralmonitoring station of the security system over the secondarycommunication link.

The security system components of an embodiment include one or more ofsensors, cameras, input/output (I/O) devices, and accessory controllers.

The premise device of an embodiment is an Internet Protocol device.

The premise device of an embodiment is a camera.

The premise device of an embodiment is a touchscreen.

The premise device of an embodiment is a device controller that controlsan attached device.

The premise device of an embodiment is a sensor.

Embodiments of the integrated security system include a methodcomprising: forming a security network by coupling a gateway to asecurity server, wherein the gateway is located at a first location andcoupled to a security system, the security system including securitysystem components located at the first location, wherein the securityserver is located at a second location different from the firstlocation; and establishing a coupling between the gateway and aplurality of premise devices located at the first location, wherein thegateway electronically integrates communications and functions of theplurality of premise devices and the security system components into thesecurity network.

Embodiments of the integrated security system include a methodcomprising: automatically establishing communications between a gatewayand a security system in a facility, wherein the security systemincludes a plurality of security system components that are proprietaryto the security system; and automatically establishing communicationsbetween the gateway and a plurality of network devices, wherein thegateway forms a premise security network at the facility and couples thepremise security network to a local area network of the facility,wherein the gateway forms the premise security network by electronicallyintegrating communications and functions of the plurality of networkdevices and the security system components.

Embodiments of the integrated security system include a methodcomprising: forming a security network by automatically establishingcommunications between a gateway and a security system, the securitysystem including security system components installed at a facility;automatically establishing communications between the security networkand a plurality of network devices located at the facility, the gatewayelectronically integrating communications and functions of the pluralityof network devices and the security system components into the securitynetwork; and providing an interface by which a remote client deviceaccesses the security network, the interface enabling communicationswith and control of the functions of the security system components andthe network devices.

Aspects of the integrated security system and corresponding systems andmethods described herein may be implemented as functionality programmedinto any of a variety of circuitry, including programmable logic devices(PLDs), such as field programmable gate arrays (FPGAs), programmablearray logic (PAL) devices, electrically programmable logic and memorydevices and standard cell-based devices, as well as application specificintegrated circuits (ASICs). Some other possibilities for implementingaspects of the integrated security system and corresponding systems andmethods include: microcontrollers with memory (such as electronicallyerasable programmable read only memory (EEPROM)), embeddedmicroprocessors, firmware, software, etc. Furthermore, aspects of theintegrated security system and corresponding systems and methods may beembodied in microprocessors having software-based circuit emulation,discrete logic (sequential and combinatorial), custom devices, fuzzy(neural) logic, quantum devices, and hybrids of any of the above devicetypes. Of course the underlying device technologies may be provided in avariety of component types, e.g., metal-oxide semiconductor field-effecttransistor (MOSFET) technologies like complementary metal-oxidesemiconductor (CMOS), bipolar technologies like emitter-coupled logic(ECL), polymer technologies (e.g., silicon-conjugated polymer andmetal-conjugated polymer-metal structures), mixed analog and digital,etc.

It should be noted that any system, method, and/or other componentsdisclosed herein may be described using computer aided design tools andexpressed (or represented), as data and/or instructions embodied invarious computer-readable media, in terms of their behavioral, registertransfer, logic component, transistor, layout geometries, and/or othercharacteristics. Computer-readable media in which such formatted dataand/or instructions may be embodied include, but are not limited to,non-volatile storage media in various forms (e.g., optical, magnetic orsemiconductor storage media) and carrier waves that may be used totransfer such formatted data and/or instructions through wireless,optical, or wired signaling media or any combination thereof. Examplesof transfers of such formatted data and/or instructions by carrier wavesinclude, but are not limited to, transfers (uploads, downloads, e-mail,etc.) over the Internet and/or other computer networks via one or moredata transfer protocols (e.g., HTTP, FTP, SMTP, etc.). When receivedwithin a computer system via one or more computer-readable media, suchdata and/or instruction-based expressions of the above describedcomponents may be processed by a processing entity (e.g., one or moreprocessors) within the computer system in conjunction with execution ofone or more other computer programs.

Unless the context clearly requires otherwise, throughout thedescription and the claims, the words “comprise,” “comprising,” and thelike are to be construed in an inclusive sense as opposed to anexclusive or exhaustive sense; that is to say, in a sense of “including,but not limited to.” Words using the singular or plural number alsoinclude the plural or singular number respectively. Additionally, thewords “herein,” “hereunder,” “above,” “below,” and words of similarimport, when used in this application, refer to this application as awhole and not to any particular portions of this application. When theword “or” is used in reference to a list of two or more items, that wordcovers all of the following interpretations of the word: any of theitems in the list, all of the items in the list and any combination ofthe items in the list.

The above description of embodiments of the integrated security systemand corresponding systems and methods is not intended to be exhaustiveor to limit the systems and methods to the precise forms disclosed.While specific embodiments of, and examples for, the integrated securitysystem and corresponding systems and methods are described herein forillustrative purposes, various equivalent modifications are possiblewithin the scope of the systems and methods, as those skilled in therelevant art will recognize. The teachings of the integrated securitysystem and corresponding systems and methods provided herein can beapplied to other systems and methods, not only for the systems andmethods described above.

The elements and acts of the various embodiments described above can becombined to provide further embodiments. These and other changes can bemade to the integrated security system and corresponding systems andmethods in light of the above detailed description.

In general, in the following claims, the terms used should not beconstrued to limit the integrated security system and correspondingsystems and methods to the specific embodiments disclosed in thespecification and the claims, but should be construed to include allsystems that operate under the claims. Accordingly, the integratedsecurity system and corresponding systems and methods is not limited bythe disclosure, but instead the scope is to be determined entirely bythe claims.

While certain aspects of the integrated security system andcorresponding systems and methods are presented below in certain claimforms, the inventors contemplate the various aspects of the integratedsecurity system and corresponding systems and methods in any number ofclaim forms. Accordingly, the inventors reserve the right to addadditional claims after filing the application to pursue such additionalclaim forms for other aspects of the integrated security system andcorresponding systems and methods.

The invention claimed is:
 1. A system comprising: a device locatedexternal to a premises; and a gateway device located at the premises andconfigured to: determine data associated with a computing device locatedat the premises; send, to a premises system located at the premises andbased on the data associated with the computing device, a message;determine, based on a response to the message, an association of thecomputing device and the premises system; and send, to the devicelocated external to the premises and based on the determination of theassociation, premises data associated with the computing device.
 2. Thesystem of claim 1, wherein the gateway device is configured to send themessage by sending the message using a protocol associated with thecomputing device, wherein the message mimics communication from thecomputing device to the premises system.
 3. The system of claim 1,wherein the message indicates that the computing device sent themessage.
 4. The system of claim 1, wherein the device located externalto the premises comprises one or more of a server, a user device, amobile device, or a phone, and wherein the computing device comprisesone or more of a security device or an automation device.
 5. The systemof claim 1, wherein the gateway device is configured to determine thedata associated with the computing device by detecting a wirelesstransmission from the computing device and determining, based on thewireless transmission, the data associated with the computing device. 6.The system of claim 1, wherein the gateway device is configured to:detect data associated with an additional computing device; send, to thepremises system and based on the data associated with the additionalcomputing device, an additional message; and determine, based on adetermination of a failure to receive a response to the additionalmessage, that the additional computing device is not associated with thepremises system.
 7. The system of claim 1, wherein the gateway device isconfigured to store data indicative of the association of the computingdevice and the premises system and send, to the device external to thepremises, the data indicative of the association.
 8. A systemcomprising: a device located external to a premises; and a gatewaydevice located at the premises and configured to: determine dataassociated with a computing device located at the premises; send, to apremises system located at the premises and based on the data associatedwith the computing device, a message; determine, based on a response tothe message, an association of the computing device and the premisessystem; store data indicative of the association of the computing deviceand the premises system; and send, to the device located external to thepremises, the data indicative of the association.
 9. The system of claim8, wherein the gateway device is configured to send the message bysending the message using a protocol associated with the computingdevice, wherein the message mimics communication from the computingdevice to the premises system.
 10. The system of claim 8, wherein themessage indicates that the computing device sent the message.
 11. Thesystem of claim 8, wherein the device located external to the premisescomprises one or more of a first server, a user device, a mobile device,or a phone, and wherein the computing device comprises one or more of asecurity device or an automation device.
 12. The system of claim 8,wherein the gateway device is configured to determine the dataassociated with the computing device by detecting a wirelesstransmission from the computing device and determining, based on thewireless transmission, the data associated with the computing device.13. The system of claim 8, wherein the gateway device is configured to:detect data associated with an additional computing device; send, to thepremises system and based on the data associated with the additionalcomputing device, an additional message; and determine, based on adetermination of a failure to receive a response to the additionalmessage, that the additional computing device is not associated with thepremises system.
 14. A non-transitory computer-readable medium storingcomputer-executable instructions that, when executed, cause:determining, by a gateway device located at a premises, data associatedwith a computing device located at the premises; sending, by the gatewaydevice, to a premises system located at the premises, and based on thedata associated with the computing device, a message; determining, basedon a response to the message, an association of the computing device andthe premises system; and sending, to a device located external to thepremises and based on the determining the association, premises dataassociated with the computing device.
 15. The non-transitorycomputer-readable medium of claim 14, wherein sending the messagecomprises sending the message using a protocol associated with thecomputing device, wherein the message mimics communication from thecomputing device to the premises system.
 16. The non-transitorycomputer-readable medium of claim 14, wherein the message indicates thatthe computing device sent the message.
 17. The non-transitorycomputer-readable medium of claim 14, wherein the device locatedexternal to the premises comprises one or more of a server, a userdevice, a mobile device, or a phone, and wherein the computing devicecomprises one or more of a security device or an automation device. 18.The non-transitory computer-readable medium of claim 14, whereindetermining data associated with the computing device comprisesdetecting a wireless transmission from the computing device anddetermining, based on the wireless transmission, the data associatedwith the computing device.
 19. The non-transitory computer-readablemedium of claim 14, wherein the instructions, when executed, furthercause: detecting, by the gateway device, data associated with anadditional computing device; sending, to the premises system and basedon the data associated with the additional computing device, anadditional message; and determining, based on a determination of afailure to receive a response to the additional message, that theadditional computing device is not associated with the premises system.20. The non-transitory computer-readable medium of claim 14, wherein theinstructions, when executed, further cause storing data indicative ofthe association of the computing device and the premises system andsending, to the device located external to the premises, the dataindicative of the association.
 21. A non-transitory computer-readablemedium storing computer-executable instructions that, when executed,cause: determining, by a gateway device located at a premises, dataassociated with a computing device located at the premises; sending, bythe gateway device, to a premises system located at the premises, andbased on the data associated with the computing device, a message;determining, based on a response to the message, an association of thecomputing device and the premises system; storing data indicative of theassociation of the computing device and the premises system; andsending, to a device located external to the premises, the dataindicative of the association.
 22. The non-transitory computer-readablemedium of claim 21, wherein sending the message comprises sending themessage using a protocol associated with the computing device, whereinthe message mimics communication from the computing device to thepremises system.
 23. The non-transitory computer-readable medium ofclaim 21, wherein the message indicates that the computing device sentthe message.
 24. The non-transitory computer-readable medium of claim21, wherein the device located external to the premises comprises one ormore of a remote server, a user device, a mobile device, or a phone, andwherein the computing device comprises one or more of a security deviceor an automation device.
 25. The non-transitory computer-readable mediumof claim 21, wherein determining data associated with the computingdevice comprises detecting a wireless transmission from the computingdevice and determining, based on the wireless transmission, the dataassociated with the computing device.
 26. The non-transitorycomputer-readable medium of claim 21, wherein the instructions, whenexecuted, further cause: detecting, by the gateway device, dataassociated with an additional computing device; sending, to the premisessystem and based on the data associated with the additional computingdevice, an additional message; and determining, based on a determinationof a failure to receive a response to the additional message, that theadditional computing device is not associated with the premises system.